Mailgun reported "EU Messaging Outage" on its status page at 2026-08-27 20:38 UTC.

When did the incident start and end?

It started at 2026-08-27 20:38 UTC and ended at 2026-08-27 21:16 UTC. It lasted 37 min.

How do I get alerts for Mailgun?

Subscribe to the Mailgun live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Mailgun. outages.live reads it every few minutes and keeps every update.

MailgunIncident · 2026-08-27 20:38 UTC

EU Messaging Outage

Q: What is affected?

Mailgun lists these components: API, Control Panel, SMTP, Outbound Delivery, Inbound email processing, Events & Logs, and 8 more.

ResolvedOfficial update

This incident has been resolved.

The latest update from Mailgun.

State

Resolved

Started

66 d ago

2026-08-27 20:38 UTC

Lasted

37 min

until 2026-08-27 21:16 UTC

Worst impact

Major outage

Timeline

4 updates

20:3820:4820:5721:0621:16

Major outageUpdate postedTimes in UTC

Investigating

6 min 17%

Identified

15 min 42%

Monitoring

16 min 42%

Updates

Times in UTC

As posted by Mailgun

Resolved2026-08-27 21:16 UTC

This incident has been resolved.

Monitoring2026-08-27 21:00 UTC

A fix has been implemented and we are monitoring the results.

Identified2026-08-27 20:45 UTC

We have identified the issue and working on restoring service.

Investigating2026-08-27 20:38 UTC

We are currently investigating an outage in our EU datacenter

Affected components

APIControl PanelSMTPOutbound DeliveryInbound email processingEvents & LogsStats and AnalyticsEmail Services - API

Mailgun in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

50 min

This incident

26% shorter than the median

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

7 h 14 min

median 50 min

90 days agoToday

Other Mailgun incidents

All incidents

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolvedresolved 4 d ago

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolvedresolved 32 d ago

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolvedresolved 48 d ago

Mailgun·EU Messaging Outage

This incident has been resolved.

Resolvedresolved 58 d ago

Mailgun·Microsoft Incident Resulting in Delivery Issues to M365

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

Resolvedresolved 58 d ago

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.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.

RSS

https://outages.cc/feed.xml?providers=mailgun

Slack

/feed subscribe https://outages.cc/feed.xml?providers=mailgun

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane