On 13 November, Netlify's support email system took 19 hours 24 minutes to clear a delivery delay affecting customers on Microsoft 365 and Outlook mailboxes. The fault sat with Microsoft's mail infrastructure, not with Netlify's own platform.
Started
10:29 UTC
Duration
Lasted 19h 24m
Source
IsDown
Next time
Netlify 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: Netlify Helpdesk
What happened?
Netlify identified the problem at 10:29 UTC and said it was aware that some support email responses to customers on Microsoft 365 and Outlook-hosted mailboxes were being delayed. The stated cause was an ongoing Microsoft Exchange Online service disruption, with messages temporarily deferred by Microsoft's mail servers before they reached your inbox. Netlify was clear that its own Support team kept processing and responding to tickets throughout, so the backlog was in delivery, not in ticket handling. The next and final update came at 18:47 UTC, over eight hours later, saying only that Netlify was monitoring email delivery and would post again once things returned to normal. That is where the public record stops. There is no further update confirming when delivery actually normalised, so the 19h 24m duration marks the span between the first notice and the last one filed, not a confirmed resolution time. Only one component appears on Netlify's status list for this incident, the Netlify Helpdesk, and no other part of the platform was named. No user reports were filed during the window on this page. Netlify's own history for the past 90 days shows 18 incidents with a median duration of 56 minutes, so an incident running over 19 hours is well outside its usual pattern, though that length reflects Microsoft's recovery timeline rather than anything happening inside Netlify's systems. Across all time, Netlify has logged 449 incidents at an average of 5.8 a month, which gives a sense of how often status updates like this one appear.
Learning
This incident sat entirely in the email layer, specifically in the path support replies take through Microsoft's Exchange Online servers, and it had nothing to do with Netlify's build pipeline, CDN, or API. UptimeRobot's own probes against Netlify's API, checked every 60 seconds from both EU and NA regions, stayed at 100% uptime across the 24 hour, 7 day and 30 day windows, and that is the correct reading: the API was never the thing that broke. A support ticket delay is invisible to any check that pings an endpoint, because there is no endpoint for "did the reply email land in Outlook". If you run a product that depends on Netlify, this is the shape to recognise: the platform can be fully reachable while a side channel like support correspondence quietly stalls for most of a day. Watching your own endpoints tells you your side is fine, it tells you nothing about whether a vendor's downstream mail delivery, ticket queue or third party dependency is stuck. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.