Exchange Online has been intermittently rejecting outbound mail to Outlook.com, Hotmail.com and Live.com addresses since 18:00 UTC. The fault sits inside Microsoft's own mail routing, and as of Microsoft's last update the incident is still open with no fix date given.
Started
18:00 UTC
Duration
Lasted 3d 11h
Source
IsDown
Next time
Microsoft 365 is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Exchange Online
What happened?
Microsoft's status page describes the problem as some users intermittently unable to send email to Outlook.com, Hotmail.com or Live.com addresses, starting 18:00 UTC. The single component affected is Exchange Online. Affected senders are getting Non-Delivery Reports back, specifically 550 5.7.1 or 550 5.7.23 errors tied to an SPF violation check on Microsoft's side. Microsoft's one update so far, posted at 05:24 UTC, says they are still gathering evidence rather than fixing anything: they are asking affected users to send fresh Network Message IDs, fresh logs and .eml examples of the failures to their support representatives. That is an active root-cause investigation, not a remediation in progress. No scope figure, percentage of tenants or geography is given beyond "some users", and Microsoft's own next update is not promised until 7:00 AM UTC on Wednesday, 11 November, several days out. No user reports were filed in this window on this page. There has been one incident logged for this day and it remains open, with no post-mortem published and no resolution time on record. Over the past 90 days Microsoft has logged 60 incidents with a median duration of 9 hours 3 minutes, and across all time the rate runs to about 8 incidents a month, so an SPF-related mail delivery fault is not unusual for this service even if this particular one is still unresolved.
Learning
This fault lives in the SPF check that Exchange Online applies before handing mail off to Outlook.com, Hotmail.com and Live.com, a server-side validation step that sits entirely outside your own infrastructure. An uptime check against your own mail server or API endpoint would show green the whole time, because your sending service is working, it is the recipient-side filtering on Microsoft's end that is rejecting the message with an NDR. That is the shape to recognise: intermittent delivery failures to one set of destination domains, with error codes pointing at the receiving system's policy checks rather than your outbound path. Our own 30-day figures for Microsoft 365 show 22 incidents with a median resolution time of 11h 22m, so slow, evidence-gathering incidents like this one are part of the normal pattern here, not an anomaly. Watching your own endpoints only tells you your half is up. UptimeRobot now also watches the provider's half, so next time mail bounces you know which side broke without guessing.