- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 100
What to do
Check whether your product depends on Mailgun. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 34m it lasted.
Anything that failed between 2026-09-04 12:20 UTC and 2026-09-04 12:54 UTC may need a replay.Subscribe to Mailgun's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mailgun works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Mailgun 3
- monitoring
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.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e2c888448a
Is Mailgun still down?
No, this incident was resolved 2026-09-04 12:54 UTC. For Mailgun's live state, see https://down.guide/mailgun.
How long did it last?
34m, from 2026-09-04 12:20 UTC to 2026-09-04 12:54 UTC, by the times Mailgun posted.
What caused it?
Mailgun hasn't published a root cause. If it does, it shows here.
Where does this come from?
Mailgun's official status page, https://status.mailgun.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.