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.958%Grade A
IncidentsEverything posted on the status page except scheduled maintenance.
91 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.
1h 35m
Since lastTime since the last counted incident was resolved.
26d 23h

By area

AProduction
8INCIDENTS
5h 57mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2 · SECURITYAug 11, 2026 · 1h 35m · regionalClick and Open Tracking Degraded (US Regions)
SEV 2Sep 14, 2026 · 58m · regionalRoute delays in EU Region
SEV 2Sep 30, 2026 · 42m · regionalRoute delays in EU Region
Most hit
Email Services - Inbound email processing4
Email Services - Outbound Delivery4
Email Services - Events & Logs4
Email Services - API2
Worse. 12 in the last 6 months, 6 in the 6 before.
AShipping
1INCIDENTS
37mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 1Aug 27, 2026 · 37m · regionalEU Messaging Outage
Most hit
Email Services - API1
Email Services - SMTP1
Email Services - Outbound Delivery1
Email Services - Inbound email processing1
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 loss1
Sev 2 · BleedingProd degraded or partly down7
Sev 3 · Can't shipCan't deploy, build or manage it0
Sev 4 · PapercutDocs, status page, slow dashboard1
1 security incident

When it breaks

Start times, last 12 months, UTC.

What breaks

Email ServicesEvents & Logs14 incidents
Email ServicesAPI8 incidents
Email ServicesInbound email processing5 incidents
Email ServicesOutbound Delivery5 incidents
Customer ToolsControl Panel4 incidents
Deliverability ServicesEmail Validation4 incidents

Where it breaks

Last 12 monthsPlaces named on the status page: cloud regions, cities, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.
1 place · 30 not pinned
Oregon (us-west1): 1 incident · Mailgun

Region only: Europe 9

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 18Sev 1–2

Incident history

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 · BACK AFTER 32M
    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 · BACK AFTER 1H 03M
    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 · BACK AFTER 2H 47M
    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 4
Elevated Timeouts for ValidationsMailgun's email validation service had elevated timeouts from 16:45 to 17:15 UTC on April 17, 2026. The cause was identified and a fix was implemented, then the incident was resolved. The update text does not describe which customers or requests were affected beyond the validation component.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 4 · 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 v11 · Oct 24, 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 SNIHTTPS requests to the Mailgun API from clients without SNI were served an expired TLS certificate, causing validation failures. The identified fix was deployed by 14:02 UTC and the incident was resolved at 15:34 UTC on 2026-04-15.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 · MEDIUM CONFIDENCE
    Clients without SNI got an expired certificate from the API for about two hours; SNI clients were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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
Apr 7, 202612mSEV 2
Elevated 500 errors on Messages endpoint in USMessages API requests returned elevated 500 errors in the US region for about 13 minutes before a fix.AI-graded · regional · Email Services - API
Why this grade
  1. RULES · SEV 2
    Sev 2 because Email Services - API had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    Messages API requests returned elevated 500 errors in the US region for about 13 minutes before a fix.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 17:30 UTC · identified
    The issue has been identified and a fix is being implemented.
  2. 17:32 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 17:42 UTC · resolved
    This incident has been resolved. Elevated 500 errors beginning at 17:25 UTC resolved at 17:30 UTC
Source
Mar 19, 202610mSEV 2
Elevated 401 errors in US RegionSome Email API requests failed with 401 errors in the US region for about 10 minutes; other regions were not mentioned as affected.AI-graded · regional · Email Services - API
Why this grade
  1. RULES · SEV 1
    Sev 1 because Email Services - API had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Some Email API requests failed with 401 errors in the US region for about 10 minutes; other regions were not mentioned as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 18:43 UTC · identified
    Some requests may be incorrectly failing with 401 error codes in our US region.
  2. 18:53 UTC · resolved
    A fix has been deployed and systems are back to normal.
Source
Mar 13, 20261h 20mSEV 2
Intermittent API Errors in US RegionMailgun's Email Services API in the US region returned intermittent errors from about 11:29 to 12:49 UTC on 13 March 2026. A fix was implemented and monitored before the incident was resolved. The text gives no further cause.AI-graded · regional · Email Services - API
Why this grade
  1. RULES · SEV 1
    Sev 1 because Email Services - API had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE · BACK AFTER 1H 04M
    Email API requests intermittently failed in the US region for about 80 minutes; other regions were not mentioned as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 11:29 UTC · investigating
    We are currently investigating this issue.
  2. 11:56 UTC · investigating
    We are continuing to investigate this issue.
  3. 12:19 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 12:33 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 12:49 UTC · resolved
    The incident has been resolved.
Source
Feb 25, 20262h 35mSEV 2
Intermittent Email Validation ErrorsMailgun's email validation API returned intermittent errors from about 19:10 to 21:45 UTC on February 25, 2026. Domain verification was also impacted. A fix was implemented around 21:36 and the incident was resolved. The provider did not give a root cause.AI-graded · one model or feature · Email Services - API +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because Email Services - API had a partial outage
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Email validation API requests intermittently failed and domain verification was also more likely to fail for about two and a half hours.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
8 updates
  1. 19:10 UTC · investigating
    We are currently investigating this issue.
  2. 19:29 UTC · investigating
    We are continuing to investigate this issue.
  3. 19:29 UTC · identified
    Domain verification is also impacted. Increased chances of domain verification failing. The issue has been identified and engineering is actively working on a fix.
  4. 19:30 UTC · identified
    We are continuing to work on a fix for this issue.
  5. 19:47 UTC · identified
    We are continuing to work on a fix for this issue.
  6. 20:25 UTC · identified
    We are continuing to work on a fix for this issue.
  7. 21:36 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  8. 21:45 UTC · resolved
    This incident has been resolved.
Source
Nov 29, 20251h 18mSEV 4
Delayed Logs in EU RegionLog delivery in Mailgun's EU region was delayed by 15 to 20 minutes; sending, receiving and webhooks worked 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
    Log delivery in Mailgun's EU region was delayed by 15 to 20 minutes; sending, receiving and webhooks worked normally.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 08:38 UTC · identified
    Logs are currently experiencing delays of 15 minutes in Mailgun's EU region. Outbound processing, inbound processing, and webhook delivery are operating normally.
  2. 09:02 UTC · identified
    Logs are currently experiencing delays of 20 minutes in Mailgun's EU region. Outbound processing, inbound processing, and webhook delivery are operating normally.
  3. 09:56 UTC · resolved
    This incident has been resolved.
Source
Nov 28, 20251h 26mSEV 4
Delayed Logs in US RegionEvent logs in Mailgun's US region ran about 15 minutes behind for roughly an hour; sending and webhooks were unaffected.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 ran about 15 minutes behind for roughly an hour; sending and webhooks were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 16:30 UTC · identified
    Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.
  2. 17:19 UTC · monitoring
    Events are processing normally, we continue to monitor as we see elevated send volumes.
  3. 17:56 UTC · resolved
    Events are processing normally.
Source
Nov 28, 202510h 46mSEV 4
Delayed Logs in EU RegionLogging events in the EU region were delayed, reaching up to 60 minutes, due to elevated sending volumes. Event processing caught up, then delays returned briefly before logs were confirmed processing normally again at 18:54 UTC. Outbound sending, inbound messages and webhooks were not impacted.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
    Log events in the EU region were delayed by up to 60 minutes; outbound sending, inbound and webhooks were not affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
29 updates
  1. 08:28 UTC · identified
    We're currently seeing delayed logging events in the EU region with up to a 15-minute delay.
  2. 08:55 UTC · identified
    We continue to see logging event delays of up to 25 minutes.
  3. 09:08 UTC · identified
    We continue to see logging event delays of up to 30 minutes.
  4. 09:32 UTC · identified
    We continue to see logging event delays of up to 40 minutes.
  5. 10:04 UTC · identified
    We continue to see logging event delays of up to 40 minutes.
  6. 10:21 UTC · identified
    We continue to see logging event delays of up to 40 minutes.
  7. 10:45 UTC · identified
    We continue to see logging event delays of up to 50 minutes.
  8. 11:13 UTC · identified
    We continue to see logging event delays of up to 55 minutes.
  9. 11:50 UTC · identified
    We continue to see logging event delays of up to 60 minutes.
  10. 12:19 UTC · identified
    We continue to see logging event delays of up to 60 minutes.
  11. 12:44 UTC · identified
    We continue to see logging event delays of up to 60 minutes.
  12. 13:04 UTC · identified
    We continue to see logging event delays of up to 60 minutes.
  13. 13:30 UTC · identified
    We continue to see logging event delays of up to 60 minutes.
  14. 13:55 UTC · identified
    We continue to see logging event delays of up to 60 minutes.
  15. 14:27 UTC · identified
    We continue to see logging event delays of up to 55 minutes.
  16. 14:32 UTC · identified
    We continue to see logging event delays of up to 50 minutes.
  17. 14:40 UTC · identified
    We continue to see logging event delays of up to 45 minutes.
  18. 14:50 UTC · identified
    We continue to see logging event delays of up to 35 minutes.
  19. 14:59 UTC · identified
    We continue to see logging event delays of up to 30 minutes.
  20. 15:09 UTC · identified
    We continue to see logging event delays of up to 20 minutes.
  21. 15:19 UTC · identified
    We continue to see logging event delays of up to 10 minutes.
  22. 15:34 UTC · identified
    We continue to see logging event delays of up to 5 minutes.
  23. 15:45 UTC · monitoring
    Event processing has caught up and delays have resolved. We continue to monitor all operations.
  24. 16:32 UTC · monitoring
    Events are processing normally, we continue to monitor as we see elevated send volumes.
  25. 17:19 UTC · monitoring
    Events are processing normally, we continue to monitor as we see elevated send volumes.
  26. 17:56 UTC · monitoring
    Logs are currently delayed by 15 minutes due to elevated sending volumes.
  27. 18:26 UTC · monitoring
    Logs are currently delayed by 20 minutes due to elevated sending volumes. Outbound sending, inbound messages, and webhooks are not impacted.
  28. 18:54 UTC · monitoring
    Events are processing normally without delay. We will continue to monitor the performance of the logging system.
  29. 19:14 UTC · resolved
    All systems are operating normally.
Source
Nov 27, 20252h 21mSEV 4
Delayed Logs in EU RegionMailgun's EU region had delayed events and logs from about 08:46 to 11:07 UTC on 27 November 2025. The text does not describe sending or delivery being affected. A fix was implemented and the backlog of delayed logging events was processed before 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 degraded performance
  2. CLAUDE · SEV 4 · REGIONAL · MEDIUM CONFIDENCE
    Event and log delivery was delayed in the EU region for about two hours; sending and delivery were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
7 updates
  1. 08:46 UTC · investigating
    We are currently investigating this issue.
  2. 09:16 UTC · investigating
    We are continuing to investigate this issue.
  3. 09:26 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 09:57 UTC · identified
    Engineers are continuing to implement a fix for this issue.
  5. 10:21 UTC · monitoring
    A fix has been implemented and we are monitoring the results. The system continues to work through the delayed logging events backlog.
  6. 10:49 UTC · monitoring
    We continue to monitor while the system processes delayed events.
  7. 11:07 UTC · resolved
    This incident has been resolved.
Source
Nov 18, 20250mSEV 2
Elevated inbound recipient rejectedMailgun wrongly rejected a subset of inbound emails with 550 'recipient rejected' errors, so senders got bounces though delivery should have succeeded. US was affected 05:14-06:41 and 14:55-15:48 UTC; EU 14:55-15:48 UTC. Logging gaps prevent exact counts.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
    Inbound emails were wrongly rejected with 550 errors for about 25% of US and 50% of EU traffic during two windows on November 13.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
1 update
  1. 10:30 UTC · resolved
    On 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 region: 05:14 to 06:41 UTC and 14:55 to 15:48 UTC EU region: 14:55 to 15:48 UTC Based on our analysis, approximately 25% of US inbound traffic and 50% of EU inbound traffic had a chance to have been impacted during these windows. We're unable to provide exact counts due to gaps in our logging for rejected inbound mail, which we have since corrected.
Source
Oct 24, 20251h 43mSEV 2
Delayed Message Processing in USSome outbound email messages in Mailgun's US region were delayed in processing starting 14:14 UTC on 2025-10-24. A fix was deployed and queues were worked through until operations returned to normal around 15:40 UTC; the incident was resolved at 15:58 UTC.AI-graded · regional · 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 · REGIONAL · HIGH CONFIDENCE
    Outbound email processing was delayed for some messages in the US region for about 1.5 hours; other regions were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 14:14 UTC · monitoring
    We have identified processing delays for some messages in our US region. A fix has been deployed and we are monitoring the recovery.
  2. 14:47 UTC · monitoring
    Queues are being worked through, we continue to monitor resolution.
  3. 15:40 UTC · monitoring
    Operations are back to normal and queues are cleared. We'll continue to monitor.
  4. 15:58 UTC · resolved
    This incident has been resolved.
Source
Oct 8, 20250mSEV 2
US Email Ingest ErrorsA deployment of new code caused the US sending pipeline to reject about 2.5% of email submissions with HTTP 500 or SMTP 451 errors between 12:55 and 13:07 UTC. The team rolled back the deployment and shifted traffic to another region, restoring normal service.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    About 2.5% of email submissions in the US region were rejected with HTTP 500 or SMTP 451 errors for about 12 minutes after a bad deploy.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
1 update
  1. 13:00 UTC · resolved
    Between 12:55 UTC and 13:07 UTC, customers may have experienced email sending failures in the US region. A deployment of new code caused our sending pipeline to temporarily reject some email submissions with HTTP 500 or SMTP 451 errors (~ 2.5% of requests). Our team quickly identified the issue, rolled back the deployment, and restored normal service. Traffic was immediately shifted from the affected US region to the non impacted region to further mitigate customer impact while the rollback took place.
Source
Sep 30, 20251h 16mSEV 3
Login issues with Mailgun ApplicationCustomers had login problems with the Mailgun control panel starting 10:57 UTC on 30 September 2025. A fix was implemented around 11:46 UTC and the incident was resolved at 12:13 UTC. The update text does not describe the root cause or give the number of users affected.AI-graded · 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 · UNCLEAR · MEDIUM CONFIDENCE
    Users had trouble logging into the Mailgun control panel for about 75 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 10:57 UTC · investigating
    We are currently investigating this issue.
  2. 11:15 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 11:46 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 11:46 UTC · monitoring
    We are continuing to monitor for any further issues.
  5. 12:13 UTC · resolved
    This incident has been resolved.
Source

Older than a year

Sep 12, 20255h 15mSEV 2
Sending errors in USSending errors hit Mailgun's US regions from about 10:07 to 15:21 UTC on September 12. A fix was deployed around 12:03, error rates normalized by 14:48, and the incident was resolved at 15:21. The text gives no root cause.AI-graded · regional · Email Services - API +1
Source
Sep 12, 20252h 00mSEV 2
Message Delays in US RegionOutbound email delivery in the US region was delayed for about two hours; the provider did not describe the delay size.AI-graded · regional · Email Services - Outbound Delivery
Source
Sep 11, 20253h 23mSEV 2
Email Validation 500sMailgun's Email Validation service returned HTTP 500 errors from about 22:56 UTC on 11 September until resolved around 02:20 UTC on 12 September. The cause was not described beyond a fix being implemented and monitored.AI-graded · Deliverability Services - Email Validation
Source
Sep 1, 202548mSEV 2
EU email delivery latencyEmails sent from Mailgun's Europe region experienced increased delivery times from about 16:23 to 17:11 UTC. Queues were worked through after a fix was deployed. Inbound routes, forwards, webhook delivery and unsubscribe processing also saw increased processing time.AI-graded · regional · Email Services - Outbound Delivery +2
Source
Aug 20, 202554mSEV 2
US email delivery latencyOutbound email from the us-east region was delivered late for about 20 minutes; the provider says it is resolved.AI-graded · regional · Email Services - Outbound Delivery
Source
Jul 29, 20252h 40mSEV 3
Partial Delay in Event ProcessingMailgun events and logs were delayed for some customers, so some events appeared late in the events and logs APIs and the customer portal. A fix was implemented at 15:45 UTC, monitoring continued, and the incident was resolved at 18:17 UTC.AI-graded · some customers · Email Services - Events & Logs
Source
Jul 21, 202511h 37mSEV 3
HTTPS Tracking Certificate Creation / Renewal blocked by Let's Encrypt OutageMailgun tracking certificate creation and renewal failed while Let's Encrypt, the issuer, had an outage. Let's Encrypt's DNS servers failed and were mitigated, and issuance then recovered under high traffic. Mailgun resolved the incident after about 11 hours.AI-graded · Email Services - API
Source
May 19, 20251h 01mSEV 2
Degraded performanceMailgun reported degraded performance across email API, SMTP, outbound delivery, inbound processing, logs and deliverability tools after an issue with one datastore. A fix was applied at 21:48Z and the incident was resolved at 22:28Z. The update text does not say service returned to normal before resolution, so no recovery timestamp is given.AI-graded · Email Services - API +9
Source
May 14, 20253h 40mSEV 2
Intermittent API ErrorsMailgun's email API, SMTP service, control panel and email validation had intermittent errors from 18:38 to 22:18 UTC on May 14, 2025. Investigators found a routing issue in their internal service mesh, deployed a fix, and resolved the incident.AI-graded · Email Services - API +3
Source
Mar 17, 202510h 24mSEV 2
Errors connecting to smtp.eu.mailgun.orgConnections to the EU SMTP endpoint failed, and the EU email API, outbound delivery and inbound processing were also affected. A mitigation restored SMTP and inbound processing at 15:02 UTC; the incident was resolved at 19:44 UTC.AI-graded · regional · Email Services - API +3
Source
Feb 10, 20251h 59mSEV 4
Intermittent Log and Event API ErrorsMailgun's logs and event APIs had degraded performance and intermittent errors starting 17:23 UTC on 2025-02-10. A fix was implemented and the incident was resolved at 19:22 UTC. The text gives no further detail on scope or cause.AI-graded · Email Services - Events & Logs
Source
Nov 14, 202430mSEV 3
Login ErrorsLogin to the control panel failed for a subset of administrative accounts for about 30 minutes; sending was not described as affected.AI-graded · some customers · Customer Tools - Control Panel
Source
Oct 17, 20248h 29mSEV 2
Europe - Email Delivery LatencyEmails sent through Mailgun's EU region were delayed from 12:12 to 20:41 UTC on 17 October 2024 due to a third-party network connectivity problem. Only customers sending from the 159.135.132.0/24 IP range were affected. Backlogs were processed at a reduced rate, and a network fix was deployed at 20:02 UTC.AI-graded · some customers · Email Services - Outbound Delivery
Source
Sep 30, 20243h 42mSEV 2
US Region(s): Elevated SMTP Connection Latency / TimeoutsSMTP sending in US regions timed out for about three hours; other regions were not reported affected.AI-graded · regional · Email Services - SMTP
Source
Aug 21, 20240mSEV 2
US Email Delivery IssueEmails sent to Mailgun's US region had a small chance of delivery failure for about four hours; other regions were not reported affected.AI-graded · regional
Source
Aug 17, 202422mSEV 3
Intermittent errors for login.mailgun.com and app.mailgun.comLogin and control panel at login.mailgun.com and app.mailgun.com had intermittent errors from 17:35 to 17:57 UTC on 17 August 2024. A fix was implemented and monitored, and the incident was resolved. The text does not say how many users were affected or what the cause was.AI-graded · Customer Tools - Control Panel
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –MapboxGrade A+99.99% up2 incidentsMTTR 12h 38mPaddleGrade 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.88% up8 incidentsMTTR 27mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.97% up2 incidentsMTTR 3h 45mInngestGrade B99.63% up14 incidentsMTTR 43mClerkGrade C99.91% up10 incidentsMTTR 3h 26mResendGrade C99.85% up26 incidentsMTTR 24mWorkOSGrade C99.56% up18 incidentsMTTR 1h 03mStytchGrade C99.83% up6 incidentsMTTR 2h 29mPlaidGrade D98.22% up18 incidentsMTTR 3h 38mTwilioGrade D98.98% up75 incidentsMTTR 9h 31m

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)