Outbound emails sent from Intercom to Microsoft addresses were delayed for 21h 23m on 12 November 2026. The fault traced back to a Microsoft outage affecting delivery through Intercom's email provider, not to anything broken inside Intercom itself.
Started
21:17 UTC
Duration
Lasted 21h 23m
Source
IsDown
Next time
Intercom 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.
What happened?
At 21:17 UTC Intercom's status page opened an investigation into reports that some outbound emails were not reaching recipients. By 22:01 UTC Intercom had identified the cause as an ongoing Microsoft outage, referencing Microsoft's own incident EX1550543, and noted that its email service provider, SparkPost, was tracking the same Microsoft issue on its own status page. Intercom said any emails that failed to deliver were being queued for periodic retry rather than dropped outright. At 09:58 UTC the next update narrowed the scope further, confirming that only delivery to Microsoft recipients was affected and that delivery to other email providers was running normally throughout. Intercom did not post anything between 22:01 and 09:58, so for roughly 12 hours the only information on record is that the queue-and-retry approach was in place. At 15:55 UTC Intercom reported that delivery to Microsoft had returned to normal levels and said it would keep monitoring, which closed out the incident at 21h 23m from first report to recovery. No components were listed as affected on Intercom's status page for this incident. No user reports were filed in the window covered by this record. There have been 9 incidents on Intercom's status page in the past 90 days, with a median duration of 27 minutes, so this one ran well past Intercom's usual pattern. No post-mortem has been published, and nothing on record explains why the Microsoft outage lasted as long as it did or what specifically broke on Microsoft's end.
Learning
This incident sat entirely in the mail delivery layer between Intercom's provider and Microsoft's inbox infrastructure, a layer that uptime checks against Intercom's own endpoints would never touch. An external check hitting Intercom's app or API would have kept reporting green the whole time, because Intercom's own systems were queuing and retrying as designed, nothing there was down. The actual symptom was invisible to availability monitoring: emails sent, accepted, then delayed somewhere downstream at a third party's mail servers. That is a common shape for outages tied to email delivery, Slack-style webhooks, or any dependency where the provider's core product stays up while a specific delivery path to a specific destination degrades. If you only watch your own product's uptime, a failure like this looks like nothing happened, while your users on Microsoft addresses were quietly not getting emails for most of a day. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.