Mailgun Outage History

32 incidents recorded over the last 365 days, 32 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Mailgun status99.93% uptime history

Every Recorded Mailgun Incident

Mailgun incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 30, 2026Route delays in EU RegionThis incident has been resolved.42 minResolved
Sep 14, 2026Route delays in EU RegionThis incident has been resolved.58 minResolved
Sep 4, 2026EU Messaging OutageThis incident has been resolved.17 minResolved
Sep 4, 2026Microsoft Incident Resulting in Delivery Issues to M365Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally.34 minResolved
Aug 31, 2026Event Log Delays in US RegionEvent queues have caught up and events are processing normally.7h 14mResolved
Aug 27, 2026EU Messaging OutageThis incident has been resolved.37 minResolved
Aug 20, 2026GCP Reporting Multi Service Outage in US-West1This incident has been resolved.1h 12mResolved
Aug 17, 2026Email Delivery Failures to Microsoft 365 DomainsWe have received confirmation that an external issue impacting email delivery to Microsoft 365 domains has been resolved. Impacted messages would have received an error stating "5.7.511 Access denied, banned sender"…0 minResolved
Aug 11, 2026Click and Open Tracking Degraded (US Regions)This incident has been resolved.1h 35mResolved
Jul 24, 2026Route delays in EU RegionAll delayed messages have been processed. Systems are operating normally1h 21mResolved
Jul 13, 2026US Email Validation 500's and Mailgun Control Panel UnavailableThis incident has been resolved.1h 32mResolved
Jul 10, 2026Mailgun Control Panel Unavailable For Some UsersThis incident has been resolved.2h 3mResolved
Jun 25, 2026Inspect previews not renderingThis incident has been resolved.1h 14mResolved
Jun 23, 2026Log retrieval errors in the US regionThis incident has been resolved.6h 55mResolved
Jun 18, 2026Partial Delay in Event Processing for US RegionThis incident has been resolved.1h 49mResolved
Jun 16, 2026Delayed logs in US regionThis incident has been resolved.3h 6mResolved
Jun 5, 2026Delayed logs in US regionThis incident has been resolved.49 minResolved
Jun 4, 2026Delayed logs in US regionThis incident has been resolved.3h 3mResolved
May 25, 2026Delayed sending in EUThis incident has been resolved.3h 36mResolved
May 6, 2026Automatic Sender Security Records Not ProvisioningThis incident has been resolved.27h 2mResolved
Apr 17, 2026Elevated Timeouts for ValidationsThis incident has been resolved.29 minResolved
Apr 15, 2026TLS Certificate Validation Errors for Clients Without SNIThis incident has been resolved.1h 54mResolved
Apr 7, 2026Elevated 500 errors on Messages endpoint in USThis incident has been resolved. Elevated 500 errors beginning at 17:25 UTC resolved at 17:30 UTC12 minResolved
Mar 19, 2026Elevated 401 errors in US RegionA fix has been deployed and systems are back to normal.10 minResolved
Mar 13, 2026Intermittent API Errors in US RegionThe incident has been resolved.1h 20mResolved
Feb 25, 2026Intermittent Email Validation ErrorsThis incident has been resolved.2h 35mResolved
Nov 29, 2025Delayed Logs in EU RegionThis incident has been resolved.1h 17mResolved
Nov 28, 2025Delayed Logs in US RegionEvents are processing normally.1h 26mResolved
Nov 28, 2025Delayed Logs in EU RegionAll systems are operating normally.10h 46mResolved
Nov 27, 2025Delayed Logs in EU RegionThis incident has been resolved.2h 20mResolved
Nov 18, 2025Elevated inbound recipient rejectedOn November 13th, Mailgun incorrectly rejected a subset of inbound emails with a 550 "recipient rejected" error. Senders received bounce notifications even though delivery should have succeeded. Affected timeframes: US…-7381 minResolved
Oct 24, 2025Delayed Message Processing in USThis incident has been resolved.1h 43mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Mailgun incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Mailgun Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Mailgun acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Mailgun outage in this window ran 1d 3h, against a mean recovery of 2h 54m. If you depend on Mailgun in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.