Event Log Delays in US Region
Event queues have caught up and events are processing normally.
The latest update from Mailgun.
State
Resolved
Started
62 d ago
2026-08-31 14:47 UTC
Lasted
7 h 14 min
until 2026-08-31 22:01 UTC
Worst impact
Degraded
Timeline
11 updatesIdentified
7 h 14 min 100%
Updates
Times in UTCAs posted by Mailgun
Event queues have caught up and events are processing normally.
The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. We expect all delays to be resolved within the hour.
The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery.
The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. We expect all delays to be resolved in the next 2 hours.
The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery.
The delays in event processing are reducing. We expect all delays to be resolved in the next 3 hours.
We are putting a fix in place for this issue. There is significant backlogs of event logs to process. We update the expected time of resolution when available.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are currently experiencing delays in event log processing in our US region.
Affected components
2Mailgun in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
9
Median duration
50 min
This incident
8.6× the median
Other Mailgun incidents
All incidentsMailgun·Route delays in EU Region
This incident has been resolved.
Mailgun·Route delays in EU Region
This incident has been resolved.
Mailgun·Route delays in EU Region
This incident has been resolved.
Mailgun·EU Messaging Outage
This incident has been resolved.
Mailgun·Microsoft Incident Resulting in Delivery Issues to M365
Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally.
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.
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.
https://outages.cc/feed.xml?providers=mailgun/feed subscribe https://outages.cc/feed.xml?providers=mailgunFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane