outages.live
Live
MailgunIncident · 2026-09-04 12:20 UTC

Microsoft Incident Resulting in Delivery Issues to M365

ResolvedOfficial update

Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally.

The latest update from Mailgun.

State

Resolved

Started

58 d ago

2026-09-04 12:20 UTC

Lasted

34 min

until 2026-09-04 12:54 UTC

Worst impact

Notice

Timeline

3 updates
12:2012:2912:3712:4612:54
NoticeUpdate postedTimes in UTC

Monitoring

34 min 100%

Updates

Times in UTC

As posted by Mailgun

Resolved2026-09-04 12:54 UTC

Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally.

Monitoring2026-09-04 12:22 UTC

We are continuing to monitor for any further issues.

Monitoring2026-09-04 12:20 UTC

Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. Sending to other email providers is not affected.

Mailgun in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

9

Median duration

50 min

This incident

32% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 h 14 min
median 50 min
90 days agoToday

Other Mailgun incidents

All incidents

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolvedresolved 4 d ago

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolvedresolved 32 d ago

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolvedresolved 48 d ago

Mailgun·EU Messaging Outage

This incident has been resolved.

Resolvedresolved 58 d ago

Mailgun·Event Log Delays in US Region

Event queues have caught up and events are processing normally.

Resolvedresolved 61 d ago

Follow Mailgun

Your coding agent knows when Mailgun is down, and tells you when a failure is theirs, not yours. You can also get Mailgun incidents in a feed reader or in Slack.

Prompt
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.cc/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 "mailgun" and tell me if Mailgun 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.

RSS
https://outages.cc/feed.xml?providers=mailgun
Slack
/feed subscribe https://outages.cc/feed.xml?providers=mailgun

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane