- Level
- confirmed
- Worst impact
- Degraded
- Components
- Outbound Delivery
- Regions
- us
- Down Index
- 12of 100
What to do
Check whether you use Mailgun Outbound Delivery in us. 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 0m it lasted.
Anything that failed between 2026-08-17 20:18 UTC and 2026-08-17 20:18 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 1
- resolved
We have received confirmation that an external issue impacting email delivery to Microsoft 365 domains has been resolved. Impacted messages would have received an error stating "5.7.511 Access denied, banned sender" between Friday, August 14th and Monday, August 17th. Any failed messages will need to be resent. Information on retrying messages can be found in our Help Center here: https://help.mailgun.com/hc/en-us/articles/18596982041883-Resending-messages
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-855a71d911
Is Mailgun still down?
No, this incident was resolved 2026-08-17 20:18 UTC. For Mailgun's live state, see https://down.guide/mailgun.
How long did it last?
0m, from 2026-08-17 20:18 UTC to 2026-08-17 20:18 UTC, by the times Mailgun posted.
What was affected?
Mailgun named Outbound Delivery in us.
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.