outages.live
Live
MailgunIncident ·

Message Delays in US Regions

DegradedOfficial update
0

Mailgun reports message delays in the US regions. The delay affects Outbound Delivery. Mailgun identified the problem and is implementing a fix.

State

Identified

Started

Ongoing for

56 min

Worst impact

Degraded

Timeline

2 updates
18:5219:0619:2019:3419:48
DegradedUpdate postedTimes in UTC

Investigating

44 min 79%

Identified

12 min 21%

Updates

Times in UTC

As posted by Mailgun

Identified

The issue has been identified and a fix is being implemented.

Investigating

We are currently investigating this issue.

Affected components

2
Outbound DeliveryEmail Services - Outbound Delivery

Mailgun in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

9

Median duration

42 min

This incident

1.3× the median

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

7 h 14 min
median 42 min
90 days agoToday

Other Mailgun incidents

All incidents

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolved

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolved

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolved

Mailgun·EU Messaging Outage

This incident has been resolved.

Resolved

Mailgun·Microsoft Incident Resulting in Delivery Issues to M365

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

Resolved

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.live/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.live/feed.xml?providers=mailgun
Slack
/feed subscribe https://outages.live/feed.xml?providers=mailgun

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane