Delayed Support Email Delivery to Microsoft 365 and Outlook Mailboxes
Netlify Helpdesk email replies to customers with Microsoft 365 and Outlook mailboxes have delivery delays. Netlify identified the issue. Netlify reports that Microsoft Exchange Online defers some messages, and Netlify monitors delivery.
State
Identified
Started
Ongoing for
19 min
Worst impact
Degraded
Timeline
1 updateIdentified
19 min 100%
Updates
Times in UTCAs posted by Netlify
We are aware that some Netlify Support email responses to customers using Microsoft 365 and Outlook-hosted mailboxes are experiencing delivery delays. These delays appear to be related to an ongoing Microsoft Exchange Online service disruption, with some messages being temporarily deferred by Microsoft's mail servers. Our Support team continues to process and respond to tickets, but affected customers may experience delays receiving our replies. We are monitoring email delivery and will provide an update as Microsoft's service recovers.
Affected components
1Netlify in the last 90 days
Full historyIncidents in 90 days
31
Days with an incident
23
Median duration
36 min
This incident
46% shorter than the median
Other Netlify incidents
All incidentsNetlify·Partially Degraded Service
Netlify reported a degraded service that affected GitHub Webhooks. Netlify reports that this incident is resolved. The incident lasted 36 minutes.
Netlify·Partially Degraded Service
Netlify reported that GitHub Webhooks had degraded performance. Netlify reports that the issue is resolved. The interruption lasted 18 minutes.
Netlify·Partially Degraded Service
Netlify reported a partially degraded service for GitHub Webhooks. Netlify resolved the incident. The outage lasted 3 minutes.
Netlify·Partially Degraded Service
Netlify reported degraded service for GitHub Webhooks. Netlify reports that the incident is resolved. The incident lasted 6 minutes.
Netlify·Partially Degraded Service
Netlify reported a partially degraded service for GitHub Webhooks. Netlify resolved the incident. The outage lasted 12 minutes.
Follow Netlify
Your coding agent knows when Netlify is down, and tells you when a failure is theirs, not yours. You can also get Netlify incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "netlify" and tell me if Netlify has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=netlify/feed subscribe https://outages.live/feed.xml?providers=netlifyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane