We don't see Smart Network Data Service statistics

Question

We don't see Smart Network Data Service statistics

Sophia Fin 0

We want to use Smart Network Data Service tool to review sending data by IP to Microsoft email addresses.

Marketing Cloud registered the IP in SNDS three days ago but i don't see data in View Data.
The registration should be successful as per support.

The emails were sent last 2 days.

0 comments

1 answer

Your answer

Answer 1

Francisco Montilla 30,700 Independent Advisor

Hello Sophia,

SNDS only reports on mail delivered to Microsoft's consumer services (Outlook/Hotmail/Live/MSN). It does not show data for Microsoft 365 work or school domains. If your last two days of sends were mainly to business tenants on Microsoft 365, "View Data" will be empty. Microsoft also updates SNDS once per day on a Pacific-time schedule, so yesterday's activity doesn't appear until after the nightly aggregation finishes.

Try to send a test from your Marketing Cloud route to a real outlook or hotmail mailbox. After it arrives, open the message's source and confirm the sending IP in the "Received from" line matches the IP you added to SNDS. Then check SNDS "View Data" the next morning once the Pacific-time job has run, in Madrid that's typically visible around 09:00-11:00 CEST. If that test message used a different egress IP than the one you registered, add the actual IP you see in the header to SNDS and use that going forward.

If you did send to consumer Outlook.com addresses and still see nothing the next day, reply here with the exact IP and I'll help you pinpoint whether Marketing Cloud used a different IP for Microsoft destinations or whether you're hitting a temporary SNDS delay.

Sophia Fin 0 Reputation points

2025-08-28T19:21:24.6433333+00:00

The IP is correct.

128.245.186.170 (mta2.info.unlimitedvacationclub.com

emails are sent from Aug 26 every day.

Could it be that the volume of sends is too low to show in SDNS?

75 per day.
Sophia Fin 0 Reputation points

2025-08-28T19:22:15.2033333+00:00

128.245.186.170
128.245.186.171
Francisco Montilla 30,700 Reputation points Independent Advisor

2025-08-28T20:14:40.44+00:00

SNDS suppresses data for IPs that send "very little mail", and Microsoft's own FAQ confirms the service only aggregates once per Pacific day and then keeps about 90 days of history. In practice, most reputable deliverability guides peg the cutoff at roughly 100 messages per IP per day to Outlook/Hotmail/Live/MSN, which means 75 total sends (or fewer if they're split across .170 and .171, or if many weren’t to consumer Microsoft domains) often yields a blank "View Data".

Do this to confirm and populate a row. On one calendar day in Pacific time, send at least 120-150 real, opted-in messages specifically to outlook or hotmail recipients from a single one of the listed IPs (e.g. keep all test mail on 128.245.186.170). Check SNDS the following morning Madrid time after the nightly Pacific aggregation completes. If you still see no data, the most likely explanations are that the mail didn't go to consumer Outlook properties or a different egress IP was used.

*Extra note: SNDS is an Outlook (consumer) telemetry surface. It does not report on Microsoft 365 business/edu delivery, and its daily job starts around midnight Pacific. That's why you can be fully registered yet see nothing when your audience is mainly corporate tenants or when volume is under the minimum.
Sophia Fin 0 Reputation points

2025-08-29T14:07:36.6+00:00

Thank you. Will check in few days. I have question about another topic related to Outlook Spam Filter and specific IP. We started the process multiple times but after some time the emails were blocked by spam filter again and again. We have bad experience with Outlook.com support and cannot get concreate answer how to fix IP reputation after not successful IP warmup and sending emails. We want to start over sending very low amount to only engaged Microsoft email addresses. 15, 15, 20, 20 etc each day

We don't have high click rate due to client web site business. But we will only send to engaged users and will have normal Open rate. Can you please help us to achieve this?

IP: 128.245.254.185
Sophia Fin 0 Reputation points

2025-08-29T14:09:57.34+00:00

thank you, i will check in few days when volume is higher.
Sophia Fin 0 Reputation points

2025-08-29T14:18:50.4333333+00:00

Thank you, I will check later when we have bigger volume
Francisco Montilla 30,700 Reputation points Independent Advisor

2025-08-29T20:18:25.4466667+00:00

Sure, Sophia!

Since this is a new topic it would help forum readers if you start a separate thread for it, but I'll give you a complete plan here so you can act right away.

Start by locking down the technical baseline before you send the first message. Publish a SPF record that explicitly authorizes 128.245.254.185 for the From domain you'll use, enable DKIM so that every message is DKIM-signed by that same domain, and publish a DMARC policy (p=none is fine to begin with) with rua reporting so you can see alignment and pass rates. Make sure reverse DNS for 128.245.254.185 resolves to a stable hostname and that your SMTP EHLO banner uses that same hostname with working forward DNS.

Next, enroll this IP in SNDS and JMRP using a monitored mailbox so you get Microsoft's daily telemetry and complaint copies.

Also, when you send, keep all Outlook/Hotmail/Live/MSN mail on 128.245.254.185 only. Do not mix that traffic with your 128.245.186.\* IPs during the warmup or you'll dilute the signal. Target only recently engaged consumer Microsoft recipients and avoid any Microsoft 365 business or school domains.

On volume, use a very gentle ramp on a single From domain and keep cadence consistent. Given your plan to start with very small daily batches, a safe opening sequence is two days at roughly 15 deliveries per day, then two days near 25 per day, then two days near 40, then two days near 60, followed by 90 per day for two days and 130 per day for two more.

Hold at any tier if SNDS shows a red filter verdict or if you receive 5.7.1 spam-related SMTP rejects, and resume only after you've identified and removed the cause using JMRP samples.

While you ramp, keep your content and list hygiene surgically clean. Send only to mailboxes that opened in the last 30-90 days, process list-unsubscribe requests quickly, and avoid sudden spikes, cross-domain link mismatches, and recycled or role addresses that drive bounces and complaints.

Each morning Madrid time, review the prior Pacific day in SNDS and your JMRP feed. If you see any complaint samples, suppress those recipients system-wide the same day. If SNDS reports persistent filtering or complaints at a tier, hold or step back the volume and correct the root cause before increasing again.

I hope this helps a bit!
Sophia Fin 0 Reputation points

2025-08-29T20:34:24.0133333+00:00

All settings are correct: SPF, DKIM, DMARK etc, see report (all green) : https://aboutmy.email/839c6d3
That is exactly the issue that we don't understand why we received 5.7.1 spam-related SMTP rejects in the first place.
The Outlook support is not helping at all.
Francisco Montilla 30,700 Reputation points Independent Advisor

2025-08-29T21:58:27.2766667+00:00

Your auth seems solid, so the 5.7.1 rejects aren't about SPF/DKIM/DMARC. They're Outlook policy blocks tied to reputation and recipient feedback. Microsoft's own postmaster page explains that 5xx rejections like SC-001/SC-004 come from IP/domain reputation, complaints, and related hygiene signals, not from passing auth alone. In other words, you have to "prove" the IP again with clean engagement, and Outlook will keep bouncing until that signal improves.

Please follow all the workarounds I suggested, I know it's kind of tedious to do, but it's required in this case.

I'll be here to continue helping after that, don't worry!
Sophia Fin 0 Reputation points

2025-09-05T21:25:41.73+00:00

We were sending welcome emails about 10-13 per day. No blocks happened recently.
Today we also sent one IP warmup email to 6 more users and all emails were blocked.

Also all welcome emails recipients from today were blocked.

Today we had total of 25 emails sent and all recipients are blocked with the same error:

5.7.1 (delivery not authorized) Unfortunately, messages from [128.245.254.185] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3150). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [Name=Protocol Filter Agent][AGT=PFA][MxId=11BBD712A926AF9C] [BL6PEPF00020E65.namprd04.prod.outlook.com 2025-09-05T18:30:32.994Z 08DDEB89562FB6F9]"

Please help us, i don't know what else I can do here.
Sophia Fin 0 Reputation points

2025-09-05T21:35:31.8866667+00:00

comment removed
Sophia Fin 0 Reputation points

2025-09-05T21:46:31.2333333+00:00

46 emails including Welcome and adhoc are blocked today. Yesterday welcome emails were not blocked.