Dev APIs / Email API / Mailgun

Mailgun

OPERATIONAL

Since Aug 2024 · 50 incidents · status.mailgun.com · checked just now

User reportsVisitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.
…
CompareAdd to stackStatus page
GradeALast 90 days
APRODASHIP

Overview

30d90d1y
Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
99.985%Grade A+
IncidentsEverything posted on the status page except scheduled maintenance.
10 Sev 1
Fully downMost customers down, by the provider's own account.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
42m
LongestLongest Sev 1–2 incident, start to resolved.
42m
Since lastTime since the last counted incident was resolved.
24d 10h

By area

A+Production
1INCIDENTS
42mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 30d
SEV 2Sep 30, 2026 · 42m · regionalRoute delays in EU Region
Most hit
Email Services - Inbound email processing1
Worse. 12 in the last 6 months, 7 in the 6 before.
A+Shipping
0INCIDENTS
0mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 30dNothing.
Worse. 6 in the last 6 months, 1 in the 6 before.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Worse. 20 in the last 6 months, 11 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down1
Sev 3 · Can't shipCan't deploy, build or manage it0
Sev 4 · PapercutDocs, status page, slow dashboard0

When it breaks

Start times, last 12 months, UTC.

What breaks

Email Services - Events & Logs14 incidents
Email Services - API8 incidents
Email Services - Inbound email processing5 incidents
Email Services - Outbound Delivery5 incidents
Customer Tools - Control Panel4 incidents
Deliverability Services - Email Validation4 incidents

Where it breaks

Last 12 monthsPlaces named on the status page: cloud regions, cities, data centres. Incidents that name none stay off the map.
1 place · 30 with none named
Oregon (us-west1): 1 incident · Mailgun
Sev 1–2 time by place, 12 monthsTime with a Sev 1 or 2 open that names the place, any provider. Overlaps count once.
Oregon1h 12m

Communication

Updates eachStatus page updates per incident, on average.
5.9Last 12 months
Update gapMedian time between status page updates during an incident.
25mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 19Sev 1–2

Incident history

Show all 34
Sep 30, 202642mSEV 2
Route delays in EU RegionInbound email route processing in Mailgun's EU Region was delayed from 09:16 to 09:58 UTC on 30 September 2026. The cause was identified and a fix was implemented, and the incident was resolved.AI-graded · regional · Email Services - Inbound email processing
Why this grade
  1. RULES · SEV 2
    Sev 2 because Email Services - Inbound email processing had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Inbound email route processing was delayed in the EU Region for about 40 minutes; other regions were not mentioned as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 09:16 UTC · investigating
    We are currently investigating this issue.
  2. 09:38 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 09:48 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 09:58 UTC · resolved
    This incident has been resolved.
Source
Sep 14, 202658mSEV 2
Route delays in EU RegionInbound email routes were delayed in the EU region for about an hour; other regions were not reported affected.AI-graded · regional · Email Services - Inbound email processing
Why this grade
  1. RULES · SEV 2
    Sev 2 because Email Services - Inbound email processing had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Inbound email routes were delayed in the EU region for about an hour; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 09:15 UTC · investigating
    We are currently investigating this issue.
  2. 09:55 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 10:13 UTC · resolved
    This incident has been resolved.
Source
Aug 27 – Sep 4, 20267d 17hSEV 1
EU Messaging Outage2 incidents
  1. Thu, Aug 27 20:38 UTC37mSEV 1
    EU Messaging OutageAn outage in Mailgun's EU datacenter disrupted email API, SMTP, outbound and inbound delivery, events, stats and the control panel from 20:38 to 21:16 UTC on 27 August. A fix was implemented around 21:00 and monitored before resolution. The update does not state a specific root cause.AI-graded · regional · Email Services - API +6
    Why this grade
    1. RULES · SEV 1
      Sev 1 because Email Services - API had a major outage
    2. CLAUDE · SEV 1 · REGIONAL · MEDIUM CONFIDENCE
      EU datacenter outage took down Mailgun email sending, SMTP, inbound, API and control panel for about 38 minutes; other regions unaffected per the text.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    4 updates
    1. 20:38 UTC · investigating
      We are currently investigating an outage in our EU datacenter
    2. 20:45 UTC · identified
      We have identified the issue and working on restoring service.
    3. 21:00 UTC · monitoring
      A fix has been implemented and we are monitoring the results.
    4. 21:16 UTC · resolved
      This incident has been resolved.
    Source
  2. Fri, Sep 4 14:16 UTC17mSEV 2
    EU Messaging OutageEmail API, SMTP, and outbound delivery were down in the EU region for about 17 minutes; other regions were not mentioned.AI-graded · regional · Email Services - API +5
    Why this grade
    1. RULES · SEV 1
      Sev 1 because Email Services - API had a major outage
    2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
      Email API, SMTP, and outbound delivery were down in the EU region for about 17 minutes; other regions were not mentioned.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    3 updates
    1. 14:16 UTC · investigating
      We are currently investigating this issue.
    2. 14:21 UTC · monitoring
      A fix has been implemented and we are monitoring the results.
    3. 14:33 UTC · resolved
      This incident has been resolved.
    Source
Sep 4, 202634mSEV 2
Microsoft Incident Resulting in Delivery Issues to M365Email to Microsoft 365 mailboxes was deferred with 451 errors across all M365 regions for hours; other providers were unaffected.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Email to Microsoft 365 mailboxes was deferred with 451 errors across all M365 regions for hours; other providers were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 12:20 UTC · monitoring
    Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. Sending to other email providers is not affected.
  2. 12:22 UTC · monitoring
    We are continuing to monitor for any further issues.
  3. 12:54 UTC · resolved
    Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally.
Source
Aug 31, 20267h 14mSEV 4
Event Log Delays in US RegionEvent log processing in Mailgun's US region was delayed from 14:47 to 22:01 UTC on August 31. Logs were late while a backlog built and drained. The text does not report message delivery failures or data loss.AI-graded · regional · Email Services - Events & Logs
Why this grade
  1. RULES · SEV 3
    Sev 3 because Email Services - Events & Logs had degraded performance
  2. CLAUDE · SEV 4 · REGIONAL · HIGH CONFIDENCE
    Event log processing ran hours behind in the US region for about seven hours; sending and other services were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
11 updates
  1. 14:47 UTC · identified
    We are currently experiencing delays in event log processing in our US region.
  2. 15:29 UTC · identified
    We are continuing to work on a fix for this issue.
  3. 16:24 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 17:05 UTC · identified
    We are continuing to work on a fix for this issue.
  5. 17:56 UTC · identified
    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.
  6. 18:59 UTC · identified
    The delays in event processing are reducing. We expect all delays to be resolved in the next 3 hours.
  7. 19:38 UTC · identified
    The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery.
  8. 20:13 UTC · identified
    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.
  9. 20:43 UTC · identified
    The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery.
  10. 21:28 UTC · identified
    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.
  11. 22:01 UTC · resolved
    Event queues have caught up and events are processing normally.
Source
Aug 20, 20261h 12mSEV 2
GCP Reporting Multi Service Outage in US-West1Mailgun saw a GCP us-west1 outage. A small number of message sends failed or were delayed, and event logs and webhooks lagged. Traffic was routed away and GCP applied a mitigation. Delayed webhooks and logs were processed, and the incident was resolved about 70 minutes after it started.AI-graded · regional · Email Services - Outbound Delivery +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Email Services - Outbound Delivery had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Outbound sends and webhooks were delayed or failed for a small number of messages in GCP us-west1 for about 70 minutes; other regions were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 16:19 UTC · monitoring
    Mailgun is monitoring service impacts in GCP's us-west1 region. We are routing traffic away from impacted infrastructure. Currently we are seeing delays in log processing and a small number of message sends.
  2. 16:30 UTC · monitoring
    Outbound delivery is operating normally. Currently there are delays for event logs and some webhooks.
  3. 17:09 UTC · monitoring
    GCP has put a mitigation in place, we are monitoring the results. At this time we are experiencing no impacts. All delayed webhooks and logs have been processed.
  4. 17:31 UTC · resolved
    This incident has been resolved.
Source
Aug 17, 20260mSEV 2
Email Delivery Failures to Microsoft 365 DomainsOutbound email to Microsoft 365 domains was rejected with banned-sender errors for several days; other mail delivery was not described as affected.AI-graded · some customers · Email Services - Outbound Delivery
Why this grade
  1. RULES · SEV 2
    Sev 2 because Email Services - Outbound Delivery had degraded performance
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Outbound email to Microsoft 365 domains was rejected with banned-sender errors for several days; other mail delivery was not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
1 update
  1. 20:18 UTC · resolved
    We 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" between Friday, August 14th and Monday, August 17th. Any failed messages will need to be resent. Information on retrying messages can be found in our Help Center here: https://help.mailgun.com/hc/en-us/articles/18596982041883-Resending-messages
Source
Aug 11, 20261h 35mSEV 2 · SECURITY
Click and Open Tracking Degraded (US Regions)A denial-of-service attack hit Mailgun's click and open tracking servers in US regions from about 05:32 to 07:07 UTC on 11 August 2026. Some tracking requests timed out or failed. A fix was implemented and the incident was resolved.AI-graded · regional · Email Services - Events & Logs
Why this grade
  1. RULES · SEV 3
    Sev 3 because Email Services - Events & Logs had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE · SECURITY
    Click and open tracking requests timed out or failed in Mailgun's US regions for about 95 minutes during a denial-of-service attack.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 05:32 UTC · investigating
    We are currently experiencing a denial of service attack against our click and open tracking servers in our US regions. Remediation work is underway. Some requests may time out or fail at this time.
  2. 05:32 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 06:54 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 07:07 UTC · resolved
    This incident has been resolved.
Source
Jul 24, 20261h 22mSEV 2
Route delays in EU RegionInbound email processed by routes in the EU Region was delayed from about 12:27 to 13:49 UTC on 24 July 2026. A fix was implemented and all delayed messages were later processed, with systems reported operating normally.AI-graded · regional · Email Services - Inbound email processing
Why this grade
  1. RULES · SEV 2
    Sev 2 because Email Services - Inbound email processing had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    Inbound messages processed by routes in the EU Region were delayed for about 80 minutes; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 12:27 UTC · investigating
    Inbound messages processed by routes are currently experiencing delays in processing.
  2. 12:38 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 13:16 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 13:18 UTC · monitoring
    A fix has been implemented and we are monitoring the results. Delayed messages are being processed.
  5. 13:49 UTC · resolved
    All delayed messages have been processed. Systems are operating normally
Source
Jul 13, 20261h 32mSEV 2
US Email Validation 500's and Mailgun Control Panel UnavailableEmail validation requests in the US returned 500 errors and the Mailgun control panel was unavailable from about 18:23 to 19:56 UTC on July 13, 2026. The provider identified the issue, deployed a fix, and resolved the incident. No root cause was given.AI-graded · regional · Customer Tools - Control Panel +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because Deliverability Services - Email Validation had a major outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    US email validation API returned 500 errors and the control panel was unavailable for about 90 minutes; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 18:23 UTC · investigating
    We are currently investigating this issue.
  2. 18:51 UTC · investigating
    We are continuing to investigate this issue.
  3. 19:24 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 19:45 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 19:56 UTC · resolved
    This incident has been resolved.
Source
Jul 10, 20262h 04mSEV 3
Mailgun Control Panel Unavailable For Some UsersMailgun's control panel was unavailable for some users from about 18:07 to 20:11 UTC on July 10, 2026. A fix was rolled out to impacted regions and the incident was resolved. The text gives no cause and does not say whether sending or the API was affected. Email Validation was listed as affected but no impact is described.AI-graded · some customers · Customer Tools - Control Panel +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because Deliverability Services - Email Validation had a major outage
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Control panel unavailable for some users for about two hours; API and sending were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
8 updates
  1. 18:07 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  2. 18:07 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 18:36 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 18:59 UTC · identified
    We are continuing to work on a fix for this issue.
  5. 19:33 UTC · identified
    We are continuing to work on a fix for this issue.
  6. 19:48 UTC · identified
    A fix is in the process of being rolled out to impacted regions.
  7. 19:58 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  8. 20:11 UTC · resolved
    This incident has been resolved.
Source
Jun 25, 20261h 15mSEV 4
Inspect previews not renderingEmail previews failed to render in Mailgun for about 75 minutes on June 25, 2026. Outbound and inbound processing, logs and webhook delivery stayed normal. A fix was deployed and the incident was resolved at 20:35 UTC.AI-graded · Deliverability Services - Email Previews
Why this grade
  1. RULES · SEV 4
    Sev 4 because Deliverability Services - Email Previews had degraded performance
  2. CLAUDE · SEV 4 · UNCLEAR · HIGH CONFIDENCE
    Email preview rendering in the dashboard failed for about 75 minutes; sending, inbound, logs and webhooks were reported normal.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 19:21 UTC · investigating
    We are currently investigating an issue with email previews not working. Outbound processing, inbound processing, logs and webhook delivery are operating normally.
  2. 20:03 UTC · investigating
    We are continuing to investigate this issue.
  3. 20:21 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 20:24 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 20:35 UTC · resolved
    This incident has been resolved.
Source
Jun 23, 20266h 55mSEV 2
Log retrieval errors in the US regionCustomers in the US region using the events/logs API or portal saw errors retrieving logs for a subset of accounts. Some also saw log delays. Outbound, inbound and webhook processing stayed normal. A fix was implemented around 15:56 UTC and the incident was resolved at 16:09 UTC on June 23, 2026.AI-graded · some customers · Email Services - Events & Logs
Why this grade
  1. RULES · SEV 3
    Sev 3 because Email Services - Events & Logs had a partial outage
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Log retrieval via API and portal failed for a subset of US-region customers for about seven hours; sending and webhooks stayed normal.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
12 updates
  1. 09:14 UTC · investigating
    Customers using the events/logs APIs or viewing logs in the customer portal may see errors in viewing or retrieving logs. These errors are only affecting a subset of our customers.
  2. 09:30 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 10:04 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 10:41 UTC · identified
    We are continuing to work on a fix for this issue.
  5. 11:19 UTC · identified
    We are continuing to work on a fix for this issue.
  6. 12:07 UTC · identified
    We are continuing to work on a fix for this issue.
  7. 13:10 UTC · identified
    We are continuing to work on a fix for this issue.
  8. 14:13 UTC · identified
    We are continuing to work on a fix for this issue.
  9. 14:52 UTC · identified
    We are continuing to work on a fix for this issue. Some customers may see log delays. Outbound processing, inbound processing, and webhook delivery are operating normally.
  10. 15:25 UTC · identified
    We are continuing to work on a fix for this issue. Some customers may see log delays. Outbound processing, inbound processing, and webhook delivery continue operating normally.
  11. 15:56 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  12. 16:09 UTC · resolved
    This incident has been resolved.
Source
Jun 16–18, 202643h 56mSEV 3
Partial Delay in Event Processing for US Region2 incidents
  1. Tue, Jun 16 14:28 UTC3h 06mSEV 4
    Delayed logs in US regionLog events in Mailgun's US region were delayed by about 15 minutes from 14:28 to 17:34 UTC on June 16. Outbound, inbound and webhook delivery stayed normal. A fix was implemented around 16:16 and the incident was resolved at 17:34.AI-graded · regional · Email Services - Events & Logs
    Why this grade
    1. RULES · SEV 3
      Sev 3 because Email Services - Events & Logs had degraded performance
    2. CLAUDE · SEV 4 · REGIONAL · MEDIUM CONFIDENCE
      Event logs in Mailgun's US region were delayed about 15 minutes for roughly three hours; sending and webhooks kept working.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    5 updates
    1. 14:28 UTC · investigating
      Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.
    2. 15:08 UTC · investigating
      We are continuing to investigate this issue.
    3. 15:48 UTC · investigating
      We are continuing to investigate this issue.
    4. 16:16 UTC · monitoring
      A fix has been implemented and we are monitoring the results.
    5. 17:34 UTC · resolved
      This incident has been resolved.
    Source
  2. Thu, Jun 18 08:34 UTC1h 50mSEV 3
    Partial Delay in Event Processing for US RegionEvents and logs in the US region were delayed for a subset of customers starting 08:34 UTC on 18 June. The provider identified the issue, deployed a fix, and resolved the incident by 10:24 UTC. Sending and delivery were not described as affected.AI-graded · some customers · Email Services - Events & Logs
    Why this grade
    1. RULES · SEV 3
      Sev 3 because Email Services - Events & Logs had degraded performance
    2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
      Event and log delivery to the events/logs API and portal was delayed for a subset of US region customers for about 2 hours.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    5 updates
    1. 08:34 UTC · investigating
      Customers using the events/logs APIs or viewing logs in the customer portal may see delays in some events appearing. These delays are only affecting a subset of our customers.
    2. 09:11 UTC · investigating
      We are continuing to investigate this issue.
    3. 09:53 UTC · identified
      The issue has been identified and a fix is being implemented.
    4. 10:11 UTC · monitoring
      A fix has been implemented and we are monitoring the results.
    5. 10:24 UTC · resolved
      This incident has been resolved.
    Source
Jun 5, 202650mSEV 4
Delayed logs in US regionEvent logs in Mailgun's US region were delayed about 15 minutes; sending, inbound and webhooks kept working normally.AI-graded · regional · Email Services - Events & Logs
Why this grade
  1. RULES · SEV 3
    Sev 3 because Email Services - Events & Logs had degraded performance
  2. CLAUDE · SEV 4 · REGIONAL · HIGH CONFIDENCE
    Event logs in Mailgun's US region were delayed about 15 minutes; sending, inbound and webhooks kept working normally.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 13:26 UTC · investigating
    Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.
  2. 14:04 UTC · monitoring
    A fix has been implemented and we are monitoring results. Outbound processing, inbound processing, and webhook delivery continue operating normally.
  3. 14:15 UTC · resolved
    This incident has been resolved.
Source
Jun 4, 20263h 03mSEV 4
Delayed logs in US regionMailgun US-region logs ran about 15 minutes behind from 18:01 UTC on 4 June 2026. Outbound, inbound and webhook delivery kept working normally. Logs were flowing normally by 20:48 and the incident was resolved at 21:04 UTC.AI-graded · regional · Email Services - Events & Logs
Why this grade
  1. RULES · SEV 3
    Sev 3 because Email Services - Events & Logs had degraded performance
  2. CLAUDE · SEV 4 · REGIONAL · HIGH CONFIDENCE
    Event logs in Mailgun's US region were delayed about 15 minutes; sending, inbound and webhooks stayed normal.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 18:01 UTC · investigating
    Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.
  2. 18:42 UTC · investigating
    We are continuing to investigate this issue.
  3. 19:52 UTC · investigating
    We are continuing to investigate this issue. Outbound processing, inbound processing, and webhook delivery continue to operate normally.
  4. 20:48 UTC · monitoring
    Logs are flowing normally and engineers continue to monitor.
  5. 21:04 UTC · resolved
    This incident has been resolved.
Source
May 25, 20263h 37mSEV 2
Delayed sending in EUMailgun's EU email sending API and outbound delivery were delayed or failing from about 12:18 to 15:55 UTC on May 25, 2026. The text does not give the root cause. A fix was deployed at several points, but the incident was only marked resolved at 15:55.AI-graded · regional · Email Services - API +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because Email Services - API had a major outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Email sending and outbound delivery were delayed or failing in the EU for about 3.5 hours; other regions were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
10 updates
  1. 12:18 UTC · investigating
    We are currently investigating this issue.
  2. 12:48 UTC · investigating
    We are continuing to investigate this issue.
  3. 12:59 UTC · investigating
    A fix has been implemented and we are monitoring the results.
  4. 13:00 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 13:38 UTC · investigating
    We are currently investigating this issue.
  6. 14:10 UTC · investigating
    We are continuing to investigate this issue.
  7. 14:46 UTC · identified
    The issue has been identified and a fix is being implemented.
  8. 15:35 UTC · identified
    We are continuing to work on a fix for this issue.
  9. 15:45 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  10. 15:55 UTC · resolved
    This incident has been resolved.
Source
May 6, 202627h 03mSEV 3
Automatic Sender Security Records Not ProvisioningCustomers creating domains with Automatic Sender Security had CNAME records created without corresponding DKIM TXT records. A fix was implemented May 7 and the incident was resolved later that day. The text does not describe impact on sending.AI-graded · some customers · Customer Tools - Control Panel
Why this grade
  1. RULES · SEV 4
    Sev 4 because Customer Tools - Control Panel had degraded performance
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Domains created with Automatic Sender Security got CNAME records without matching DKIM TXT records, blocking domain setup for about 27 hours; sending was not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 15:40 UTC · identified
    Customers creating domains with Automatic Sender Security may have CNAME records with no corresponding TXT records reflecting DKIM keys. A fix for this issue is being prepared.
  2. 19:46 UTC · identified
    We are continuing to work on a fix for this issue.
  3. 12:40 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 18:42 UTC · resolved
    This incident has been resolved.
Source
Apr 17, 202629mSEV 2
Elevated Timeouts for ValidationsMailgun's email validation service had elevated timeouts starting 16:45 UTC on 2026-04-17. A fix was implemented and monitored, and the incident was resolved at 17:15 UTC. The provider did not describe the number of affected customers.AI-graded · Deliverability Services - Email Validation
Why this grade
  1. RULES · SEV 2
    Sev 2 because Deliverability Services - Email Validation had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Email validation API requests timed out for about 30 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 16:45 UTC · identified
    The issue has been identified and a fix is being implemented.
  2. 17:05 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 17:05 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 17:15 UTC · resolved
    This incident has been resolved.
Source
Apr 15, 20261h 54mSEV 2
TLS Certificate Validation Errors for Clients Without SNIMailgun presented an expired TLS certificate to HTTPS API clients that did not send SNI, causing certificate validation failures. The fix was deployed around 14:02 UTC and the incident was resolved at 15:34 UTC on April 15, 2026.AI-graded · some customers · Email Services - API
Why this grade
  1. RULES · SEV 1
    Sev 1 because Email Services - API had a partial outage
  2. CLAUDE · SEV 2 · SUBSET · HIGH CONFIDENCE
    Email API requests from clients without SNI failed certificate validation for about two hours; clients with SNI were unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 13:40 UTC · investigating
    We are currently investigating an issue where customers making HTTPS requests to our API without Server Name Indication (SNI) enabled are being presented with an expired SSL/TLS certificate. This results in certificate validation failures for affected clients.
  2. 13:42 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 14:02 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 15:34 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –PaddleGrade A+100.00% up3 incidentsMTTR 47mLoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mAblyGrade A99.97% up7 incidentsMTTR 7mMailgunGrade A99.95% up9 incidentsMTTR 42mPusherGrade A99.96% up2 incidentsMTTR 3h 45mInngestGrade B99.59% up14 incidentsMTTR 43mMapboxGrade C99.91% up2 incidentsMTTR 12h 38mResendGrade C98.67% up25 incidentsMTTR 24mClerkGrade C99.90% up10 incidentsMTTR 3h 26mStytchGrade C99.79% up7 incidentsMTTR 57mWorkOSGrade C99.34% up21 incidentsMTTR 1h 05mPlaidGrade F98.13% up18 incidentsMTTR 3h 38mTwilioGrade F96.31% up58 incidentsMTTR 7h 26m

README badge

Mailgun's live grade, for your README.

Mailgun grade badge
[![mailgun on downagain.dev](https://downagain.dev/badge/mailgun.svg)](https://downagain.dev/p/mailgun)