- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Mailgun 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 2025-10-08 15:00 UTC and 2025-10-08 13:00 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
Between 12:55 UTC and 13:07 UTC, customers may have experienced email sending failures in the US region. A deployment of new code caused our sending pipeline to temporarily reject some email submissions with HTTP 500 or SMTP 451 errors (~ 2.5% of requests). Our team quickly identified the issue, rolled back the deployment, and restored normal service. Traffic was immediately shifted from the affected US region to the non impacted region to further mitigate customer impact while the rollback took place.
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-3e46ad1420
Is Mailgun still down?
No, this incident was resolved 2025-10-08 13:00 UTC. For Mailgun's live state, see https://down.guide/mailgun.
How long did it last?
0m, from 2025-10-08 15:00 UTC to 2025-10-08 13:00 UTC, by the times Mailgun posted.
What was affected?
Mailgun named 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.