Live

Mailgun

Mailgun is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

10

Days with an incident

9

Median duration

50 min

Longest incident

7 h 14 min

Components

11

Email Services

API Operational
90 days ago2 days with an incidentToday
SMTP Operational
90 days ago2 days with an incidentToday
Outbound Delivery Operational
90 days ago4 days with an incidentToday
Inbound email processing Operational
90 days ago5 days with an incidentToday
Events & Logs Operational
90 days ago5 days with an incidentToday
Stats and Analytics Operational
90 days ago2 days with an incidentToday

Customer Tools

Control Panel Operational
90 days ago1 day with an incidentToday

Deliverability Services

Email Validation Operational
90 days agoNo incidentsToday
Inbox Placement Operational
90 days agoNo incidentsToday
Spam Trap Network Operational
90 days agoNo incidentsToday
Email Previews Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane