Mailgun

Affected: Inbound email processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-30 09:16 UTC

   We are currently investigating this issue.

2. identified 2026-09-30 09:38 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-30 09:48 UTC

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

4. resolved 2026-09-30 09:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Inbound email processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 09:15 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-14 09:55 UTC

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

3. resolved 2026-09-14 10:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API, SMTP, Outbound Delivery, Inbound email processing, Events & Logs, Stats and Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-04 14:16 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-04 14:21 UTC

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

3. resolved 2026-09-04 14:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-04 12:20 UTC

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

2. monitoring 2026-09-04 12:22 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-09-04 12:54 UTC

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

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-31 14:47 UTC

   We are currently experiencing delays in event log processing in our US region.

2. identified 2026-08-31 15:29 UTC

   We are continuing to work on a fix for this issue.

3. identified 2026-08-31 16:24 UTC

   We are continuing to work on a fix for this issue.

4. identified 2026-08-31 17:05 UTC

   We are continuing to work on a fix for this issue.

5. identified 2026-08-31 17:56 UTC

   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. identified 2026-08-31 18:59 UTC

   The delays in event processing are reducing. We expect all delays to be resolved in the next 3 hours.

7. identified 2026-08-31 19:38 UTC

   The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery.

8. identified 2026-08-31 20:13 UTC

   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. identified 2026-08-31 20:43 UTC

   The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery.

10. identified 2026-08-31 21:28 UTC

    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. resolved 2026-08-31 22:01 UTC

    Event queues have caught up and events are processing normally.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API, Control Panel, SMTP, Outbound Delivery, Inbound email processing, Events & Logs, Stats and Analytics

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 20:38 UTC

   We are currently investigating an outage in our EU datacenter

2. identified 2026-08-27 20:45 UTC

   We have identified the issue and working on restoring service.

3. monitoring 2026-08-27 21:00 UTC

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

4. resolved 2026-08-27 21:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Outbound Delivery, Events & Logs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. monitoring 2026-08-20 16:19 UTC

   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. monitoring 2026-08-20 16:30 UTC

   Outbound delivery is operating normally. Currently there are delays for event logs and some webhooks.

3. monitoring 2026-08-20 17:09 UTC

   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. resolved 2026-08-20 17:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Outbound Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-17 20:18 UTC

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

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-11 05:32 UTC

   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. identified 2026-08-11 05:32 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-11 06:54 UTC

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

4. resolved 2026-08-11 07:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Inbound email processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-24 12:27 UTC

   Inbound messages processed by routes are currently experiencing delays in processing.

2. identified 2026-07-24 12:38 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-07-24 13:16 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2026-07-24 13:18 UTC

   A fix has been implemented and we are monitoring the results. Delayed messages are being processed.

5. resolved 2026-07-24 13:49 UTC

   All delayed messages have been processed. Systems are operating normally

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Control Panel, Email Validation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 18:23 UTC

   We are currently investigating this issue.

2. investigating 2026-07-13 18:51 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-13 19:24 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-07-13 19:45 UTC

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

5. resolved 2026-07-13 19:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Control Panel, Email Validation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-10 18:07 UTC

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

2. identified 2026-07-10 18:07 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-07-10 18:36 UTC

   We are continuing to work on a fix for this issue.

4. identified 2026-07-10 18:59 UTC

   We are continuing to work on a fix for this issue.

5. identified 2026-07-10 19:33 UTC

   We are continuing to work on a fix for this issue.

6. identified 2026-07-10 19:48 UTC

   A fix is in the process of being rolled out to impacted regions.

7. monitoring 2026-07-10 19:58 UTC

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

8. resolved 2026-07-10 20:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Email Previews

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 19:21 UTC

   We are currently investigating an issue with email previews not working. Outbound processing, inbound processing, logs and webhook delivery are operating normally.

2. investigating 2026-06-25 20:03 UTC

   We are continuing to investigate this issue.

3. identified 2026-06-25 20:21 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-06-25 20:24 UTC

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

5. resolved 2026-06-25 20:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-23 09:14 UTC

   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. identified 2026-06-23 09:30 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-06-23 10:04 UTC

   We are continuing to work on a fix for this issue.

4. identified 2026-06-23 10:41 UTC

   We are continuing to work on a fix for this issue.

5. identified 2026-06-23 11:19 UTC

   We are continuing to work on a fix for this issue.

6. identified 2026-06-23 12:07 UTC

   We are continuing to work on a fix for this issue.

7. identified 2026-06-23 13:10 UTC

   We are continuing to work on a fix for this issue.

8. identified 2026-06-23 14:13 UTC

   We are continuing to work on a fix for this issue.

9. identified 2026-06-23 14:52 UTC

   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. identified 2026-06-23 15:25 UTC

    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. monitoring 2026-06-23 15:56 UTC

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

12. resolved 2026-06-23 16:09 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 08:34 UTC

   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. investigating 2026-06-18 09:11 UTC

   We are continuing to investigate this issue.

3. identified 2026-06-18 09:53 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-06-18 10:11 UTC

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

5. resolved 2026-06-18 10:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-16 14:28 UTC

   Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.

2. investigating 2026-06-16 15:08 UTC

   We are continuing to investigate this issue.

3. investigating 2026-06-16 15:48 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-06-16 16:16 UTC

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

5. resolved 2026-06-16 17:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-05 13:26 UTC

   Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.

2. monitoring 2026-06-05 14:04 UTC

   A fix has been implemented and we are monitoring results. Outbound processing, inbound processing, and webhook delivery continue operating normally.

3. resolved 2026-06-05 14:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 18:01 UTC

   Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.

2. investigating 2026-06-04 18:42 UTC

   We are continuing to investigate this issue.

3. investigating 2026-06-04 19:52 UTC

   We are continuing to investigate this issue. Outbound processing, inbound processing, and webhook delivery continue to operate normally.

4. monitoring 2026-06-04 20:48 UTC

   Logs are flowing normally and engineers continue to monitor.

5. resolved 2026-06-04 21:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API, Outbound Delivery

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-25 12:18 UTC

   We are currently investigating this issue.

2. investigating 2026-05-25 12:48 UTC

   We are continuing to investigate this issue.

3. investigating 2026-05-25 12:59 UTC

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

4. monitoring 2026-05-25 13:00 UTC

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

5. investigating 2026-05-25 13:38 UTC

   We are currently investigating this issue.

6. investigating 2026-05-25 14:10 UTC

   We are continuing to investigate this issue.

7. identified 2026-05-25 14:46 UTC

   The issue has been identified and a fix is being implemented.

8. identified 2026-05-25 15:35 UTC

   We are continuing to work on a fix for this issue.

9. monitoring 2026-05-25 15:45 UTC

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

10. resolved 2026-05-25 15:55 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Control Panel

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-06 15:40 UTC

   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. identified 2026-05-06 19:46 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-05-07 12:40 UTC

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

4. resolved 2026-05-07 18:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Email Validation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-17 16:45 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-04-17 17:05 UTC

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

3. monitoring 2026-04-17 17:05 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-04-17 17:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-15 13:40 UTC

   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. identified 2026-04-15 13:42 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-15 14:02 UTC

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

4. resolved 2026-04-15 15:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-07 17:30 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-04-07 17:32 UTC

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

3. resolved 2026-04-07 17:42 UTC

   This incident has been resolved. Elevated 500 errors beginning at 17:25 UTC resolved at 17:30 UTC

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-19 18:43 UTC

   Some requests may be incorrectly failing with 401 error codes in our US region.

2. resolved 2026-03-19 18:53 UTC

   A fix has been deployed and systems are back to normal.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-13 11:29 UTC

   We are currently investigating this issue.

2. investigating 2026-03-13 11:56 UTC

   We are continuing to investigate this issue.

3. identified 2026-03-13 12:19 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-03-13 12:33 UTC

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

5. resolved 2026-03-13 12:49 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API, Email Validation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-25 19:10 UTC

   We are currently investigating this issue.

2. investigating 2026-02-25 19:29 UTC

   We are continuing to investigate this issue.

3. identified 2026-02-25 19:29 UTC

   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. identified 2026-02-25 19:30 UTC

   We are continuing to work on a fix for this issue.

5. identified 2026-02-25 19:47 UTC

   We are continuing to work on a fix for this issue.

6. identified 2026-02-25 20:25 UTC

   We are continuing to work on a fix for this issue.

7. monitoring 2026-02-25 21:36 UTC

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

8. resolved 2026-02-25 21:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-29 08:38 UTC

   Logs are currently experiencing delays of 15 minutes in Mailgun's EU region. Outbound processing, inbound processing, and webhook delivery are operating normally.

2. identified 2025-11-29 09:02 UTC

   Logs are currently experiencing delays of 20 minutes in Mailgun's EU region. Outbound processing, inbound processing, and webhook delivery are operating normally.

3. resolved 2025-11-29 09:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-28 16:30 UTC

   Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.

2. monitoring 2025-11-28 17:19 UTC

   Events are processing normally, we continue to monitor as we see elevated send volumes.

3. resolved 2025-11-28 17:56 UTC

   Events are processing normally.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-28 08:28 UTC

   We're currently seeing delayed logging events in the EU region with up to a 15-minute delay.

2. identified 2025-11-28 08:55 UTC

   We continue to see logging event delays of up to 25 minutes.

3. identified 2025-11-28 09:08 UTC

   We continue to see logging event delays of up to 30 minutes.

4. identified 2025-11-28 09:32 UTC

   We continue to see logging event delays of up to 40 minutes.

5. identified 2025-11-28 10:04 UTC

   We continue to see logging event delays of up to 40 minutes.

6. identified 2025-11-28 10:21 UTC

   We continue to see logging event delays of up to 40 minutes.

7. identified 2025-11-28 10:45 UTC

   We continue to see logging event delays of up to 50 minutes.

8. identified 2025-11-28 11:13 UTC

   We continue to see logging event delays of up to 55 minutes.

9. identified 2025-11-28 11:50 UTC

   We continue to see logging event delays of up to 60 minutes.

10. identified 2025-11-28 12:19 UTC

    We continue to see logging event delays of up to 60 minutes.

11. identified 2025-11-28 12:44 UTC

    We continue to see logging event delays of up to 60 minutes.

12. identified 2025-11-28 13:04 UTC

    We continue to see logging event delays of up to 60 minutes.

13. identified 2025-11-28 13:30 UTC

    We continue to see logging event delays of up to 60 minutes.

14. identified 2025-11-28 13:55 UTC

    We continue to see logging event delays of up to 60 minutes.

15. identified 2025-11-28 14:27 UTC

    We continue to see logging event delays of up to 55 minutes.

16. identified 2025-11-28 14:32 UTC

    We continue to see logging event delays of up to 50 minutes.

17. identified 2025-11-28 14:40 UTC

    We continue to see logging event delays of up to 45 minutes.

18. identified 2025-11-28 14:50 UTC

    We continue to see logging event delays of up to 35 minutes.

19. identified 2025-11-28 14:59 UTC

    We continue to see logging event delays of up to 30 minutes.

20. identified 2025-11-28 15:09 UTC

    We continue to see logging event delays of up to 20 minutes.

21. identified 2025-11-28 15:19 UTC

    We continue to see logging event delays of up to 10 minutes.

22. identified 2025-11-28 15:34 UTC

    We continue to see logging event delays of up to 5 minutes.

23. monitoring 2025-11-28 15:45 UTC

    Event processing has caught up and delays have resolved. We continue to monitor all operations.

24. monitoring 2025-11-28 16:32 UTC

    Events are processing normally, we continue to monitor as we see elevated send volumes.

25. monitoring 2025-11-28 17:19 UTC

    Events are processing normally, we continue to monitor as we see elevated send volumes.

26. monitoring 2025-11-28 17:56 UTC

    Logs are currently delayed by 15 minutes due to elevated sending volumes.

27. monitoring 2025-11-28 18:26 UTC

    Logs are currently delayed by 20 minutes due to elevated sending volumes. Outbound sending, inbound messages, and webhooks are not impacted.

28. monitoring 2025-11-28 18:54 UTC

    Events are processing normally without delay. We will continue to monitor the performance of the logging system.

29. resolved 2025-11-28 19:14 UTC

    All systems are operating normally.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-27 08:46 UTC

   We are currently investigating this issue.

2. investigating 2025-11-27 09:16 UTC

   We are continuing to investigate this issue.

3. identified 2025-11-27 09:26 UTC

   The issue has been identified and a fix is being implemented.

4. identified 2025-11-27 09:57 UTC

   Engineers are continuing to implement a fix for this issue.

5. monitoring 2025-11-27 10:21 UTC

   A fix has been implemented and we are monitoring the results. The system continues to work through the delayed logging events backlog.

6. monitoring 2025-11-27 10:49 UTC

   We continue to monitor while the system processes delayed events.

7. resolved 2025-11-27 11:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-11-13 10:30 UTC

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

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Outbound Delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-10-24 14:14 UTC

   We have identified processing delays for some messages in our US region. A fix has been deployed and we are monitoring the recovery.

2. monitoring 2025-10-24 14:47 UTC

   Queues are being worked through, we continue to monitor resolution.

3. monitoring 2025-10-24 15:40 UTC

   Operations are back to normal and queues are cleared. We'll continue to monitor.

4. resolved 2025-10-24 15:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-10-08 13:00 UTC

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

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Control Panel

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-30 10:57 UTC

   We are currently investigating this issue.

2. identified 2025-09-30 11:15 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-09-30 11:46 UTC

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

4. monitoring 2025-09-30 11:46 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-09-30 12:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-12 10:07 UTC

   We are currently investigating reports of sending errors in US regions.

2. investigating 2025-09-12 10:28 UTC

   We are continuing to investigate this issue.

3. investigating 2025-09-12 10:49 UTC

   We are continuing to investigate this issue.

4. investigating 2025-09-12 11:14 UTC

   We are continuing to investigate this issue.

5. monitoring 2025-09-12 12:03 UTC

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

6. identified 2025-09-12 12:57 UTC

   We are continuing to work to stabilize things at this time. We have no ETA.

7. identified 2025-09-12 13:42 UTC

   Error rates are normalizing as we continue to work to fix the issue.

8. monitoring 2025-09-12 13:57 UTC

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

9. monitoring 2025-09-12 14:48 UTC

   Systems have normalized, we are continuing to monitor for any issues.

10. resolved 2025-09-12 15:21 UTC

    All systems are operating normally at this time. Our engineers continue to monitor our systems for any recurrence or new issues.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Outbound Delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-12 06:26 UTC

   We are currently investigating this issue.

2. monitoring 2025-09-12 07:29 UTC

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

3. resolved 2025-09-12 08:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Email Validation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-11 22:56 UTC

   We are currently investigating this issue.

2. identified 2025-09-12 00:15 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-09-12 01:00 UTC

   The issue has been identified and we continue to work on a fix for this issue.

4. monitoring 2025-09-12 02:07 UTC

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

5. monitoring 2025-09-12 02:07 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-09-12 02:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Outbound Delivery, Inbound email processing, Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-01 16:23 UTC

   Email's sent from our Europe region may be experiencing increased delivery times. We are currently investigating.

2. identified 2025-09-01 16:25 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-09-01 16:31 UTC

   We are continuing to work on a fix for this issue.

4. identified 2025-09-01 16:38 UTC

   We are continuing to work on a fix for this issue.

5. monitoring 2025-09-01 16:38 UTC

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

6. monitoring 2025-09-01 16:53 UTC

   Queues are being worked through. Normal email delivery times will resume shortly. In addition to delayed email delivery, these other parts of our system saw increased processing time as well: inbound routes, forwards, webhook delivery, and unsubscribe processing.

7. resolved 2025-09-01 17:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Outbound Delivery

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-08-20 16:20 UTC

   Email's from our us-east region may have experienced longer delivery time between 16:00 UTC and 16:20 UTC. The issue is resolved and we are monitoring.

2. monitoring 2025-08-20 16:27 UTC

   Services are fully operational.

3. resolved 2025-08-20 17:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-07-29 15:37 UTC

   Customers using the events or logs APIs or viewing logs in the customer portal may see delays in some events appearing.

2. monitoring 2025-07-29 15:45 UTC

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

3. monitoring 2025-07-29 17:54 UTC

   We are continuing to monitor the system as delays resolve

4. resolved 2025-07-29 18:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-21 23:56 UTC

   Let's Encrypt, the certificate issuer used for creating certificates on customer tracking domains is experiencing an outage (https://letsencrypt.status.io/). Attempting to generate or regenerate a tracking certificate will not succeed until service is restored.

2. monitoring 2025-07-22 05:22 UTC

   The current status of Let's Encrypt infrastucture is "[Identified] We have deployed mitigations for the failure of our internal DNS servers. Issuance of certificates is now succeeding, though we are still recovering from the resulting high traffic volumes." We are monitoring the...

3. resolved 2025-07-22 11:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API, Email Validation, SMTP, Inbox Placement, Outbound Delivery, Spam Trap Network, Inbound email processing, Email Previews, Events & Logs, Stats and Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-19 21:27 UTC

   We are currently investigating reports of degraded performance.

2. identified 2025-05-19 21:33 UTC

   We have identified an issue with one of our datastores and are attempting to implement a fix.

3. monitoring 2025-05-19 21:48 UTC

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

4. resolved 2025-05-19 22:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API, Control Panel, Email Validation, SMTP

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-14 18:38 UTC

   We are currently investigating this issue.

2. investigating 2025-05-14 18:48 UTC

   We are continuing to investigate this issue.

3. investigating 2025-05-14 19:12 UTC

   We are continuing to investigate this issue.

4. investigating 2025-05-14 20:41 UTC

   We are continuing to investigate this issue.

5. investigating 2025-05-14 21:08 UTC

   We are continuing to investigate this issue.

6. identified 2025-05-14 21:32 UTC

   We identified a routing issue in our internal service mesh. We are attempting to roll out a fix.

7. monitoring 2025-05-14 22:03 UTC

   A fix has been deployed and we are monitoring.

8. resolved 2025-05-14 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: API, SMTP, Outbound Delivery, Inbound email processing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-17 09:20 UTC

   We are currently investigating this issue.

2. investigating 2025-03-17 09:48 UTC

   We are continuing to investigate this issue.

3. investigating 2025-03-17 10:29 UTC

   We are continuing to investigate this issue.

4. identified 2025-03-17 11:56 UTC

   The issue has been identified and a fix is being implemented.

5. identified 2025-03-17 14:22 UTC

   We are continuing to work on a fix for this issue.

6. monitoring 2025-03-17 15:02 UTC

   A mitigation has been put in place and SMTP / Inbound email processing in our EU region is back to full working behavior.

7. monitoring 2025-03-17 18:43 UTC

   We are continuing to monitor for any further issues.

8. resolved 2025-03-17 19:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Events & Logs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-10 17:23 UTC

   Our team is investigating degraded performance in our logs and event APIs.

2. monitoring 2025-02-10 19:19 UTC

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

3. monitoring 2025-02-10 19:20 UTC

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

4. resolved 2025-02-10 19:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Control Panel

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-14 23:58 UTC

   Our team is investigating reports of Login issues for a subset of administrative accounts

2. investigating 2024-11-15 00:26 UTC

   Our team has resolved the login issue.

3. resolved 2024-11-15 00:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Outbound Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-10-17 12:12 UTC

   Due to network connectivity issues with a third party, there is a chance that emails being sent through Mailgun's EU region are experiencing delivery delays. The issue has been identified and a fix is in progress.

2. identified 2024-10-17 13:34 UTC

   We are continuing to work with our networking partner on the fix. Only customers sending with IPs in the 159.135.132.0/24 range are impacted.

3. monitoring 2024-10-17 15:30 UTC

   Connectivity has been restored, we are monitoring the traffic backlog as sending resumes.

4. monitoring 2024-10-17 17:26 UTC

   We are continuing to process the sending backlog at a reduced rate while things recover. Delays for the affected network should still be expected.

5. identified 2024-10-17 17:36 UTC

   Further mitigations are being worked on to resolve networking issues, messages will continue to be delayed until a full fix is implemented.

6. identified 2024-10-17 19:15 UTC

   We are continuing to work with our network provider to bring this range online.

7. monitoring 2024-10-17 20:02 UTC

   A fix has been implemented and traffic is sending through these networks. We are monitoring the resolution.

8. resolved 2024-10-17 20:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: SMTP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-30 20:47 UTC

   We are currently experiencing elevated timeouts when sending email via SMTP in US regions. Investigation is underway.

2. monitoring 2024-09-30 23:38 UTC

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

3. resolved 2024-10-01 00:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-08-20 19:00 UTC

   On August 20th, 2024, between 18:45 - 22:45 UTC, emails submitted to our US region experienced a small chance of delivery failure. Please review your email Events for "602 Too old message" errors to identify any affected emails and resend them if necessary. The issue was...

Excerpts are shortened. Read the full incident on Mailgun's status page.

Affected: Control Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-17 17:35 UTC

   We are currently investigating this issue.

2. identified 2024-08-17 17:35 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-08-17 17:52 UTC

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

4. monitoring 2024-08-17 17:55 UTC

   We are continuing to monitor for any further issues.

5. resolved 2024-08-17 17:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mailgun's status page.