Historial de interrupciones de Mailgun

1. 11 de agosto de 2026 a las 5:32 UTCinvestigating

   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. 11 de agosto de 2026 a las 5:32 UTCidentified

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

3. 11 de agosto de 2026 a las 6:54 UTCmonitoring

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

4. 11 de agosto de 2026 a las 7:07 UTCresolved

   This incident has been resolved.

1. 24 de julio de 2026 a las 12:27 UTCinvestigating

   Los mensajes entrantes tratados por rutas están experimentando retrasos en el procesamiento.

2. 24 de julio de 2026 a las 12:38 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 24 de julio de 2026 a las 13:16 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

4. 24 de julio de 2026 a las 13:18 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados. Se están procesando mensajes dilatados.

5. 24 de julio de 2026 a las 13:49 UTCresolved

   Todos los mensajes retrasados han sido procesados. Los sistemas funcionan normalmente

Traducido automáticamente desde la actualización oficial del incidente.

1. 13 de julio de 2026 a las 18:23 UTCinvestigating

   We are currently investigating this issue.

2. 13 de julio de 2026 a las 18:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 de julio de 2026 a las 19:24 UTCidentified

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

4. 13 de julio de 2026 a las 19:45 UTCmonitoring

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

5. 13 de julio de 2026 a las 19:56 UTCresolved

   This incident has been resolved.

1. 10 de julio de 2026 a las 18:07 UTCidentified

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

2. 10 de julio de 2026 a las 19:33 UTCidentified

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

3. 10 de julio de 2026 a las 19:48 UTCidentified

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

4. 10 de julio de 2026 a las 19:58 UTCmonitoring

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

5. 10 de julio de 2026 a las 20:11 UTCresolved

   This incident has been resolved.

1. 25 de junio de 2026 a las 19:21 UTCinvestigating

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

2. 25 de junio de 2026 a las 20:03 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 de junio de 2026 a las 20:21 UTCidentified

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

4. 25 de junio de 2026 a las 20:24 UTCmonitoring

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

5. 25 de junio de 2026 a las 20:35 UTCresolved

   This incident has been resolved.

1. 23 de junio de 2026 a las 9:14 UTCinvestigating

   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. 23 de junio de 2026 a las 9:30 UTCidentified

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

3. 23 de junio de 2026 a las 14:13 UTCidentified

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

4. 23 de junio de 2026 a las 14:52 UTCidentified

   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.

5. 23 de junio de 2026 a las 15:25 UTCidentified

   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.

6. 23 de junio de 2026 a las 15:56 UTCmonitoring

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

7. 23 de junio de 2026 a las 16:09 UTCresolved

   This incident has been resolved.

1. 18 de junio de 2026 a las 8:34 UTCinvestigating

   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. 18 de junio de 2026 a las 9:11 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 de junio de 2026 a las 9:53 UTCidentified

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

4. 18 de junio de 2026 a las 10:11 UTCmonitoring

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

5. 18 de junio de 2026 a las 10:24 UTCresolved

   This incident has been resolved.

1. 16 de junio de 2026 a las 14:28 UTCinvestigating

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

2. 16 de junio de 2026 a las 15:48 UTCinvestigating

   We are continuing to investigate this issue.

3. 16 de junio de 2026 a las 16:16 UTCmonitoring

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

4. 16 de junio de 2026 a las 17:34 UTCresolved

   This incident has been resolved.

1. 5 de junio de 2026 a las 13:26 UTCinvestigating

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

2. 5 de junio de 2026 a las 14:04 UTCmonitoring

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

3. 5 de junio de 2026 a las 14:15 UTCresolved

   This incident has been resolved.

1. 4 de junio de 2026 a las 18:01 UTCinvestigating

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

2. 4 de junio de 2026 a las 18:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 de junio de 2026 a las 19:52 UTCinvestigating

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

4. 4 de junio de 2026 a las 20:48 UTCmonitoring

   Logs are flowing normally and engineers continue to monitor.

5. 4 de junio de 2026 a las 21:04 UTCresolved

   This incident has been resolved.

1. 25 de mayo de 2026 a las 12:59 UTCinvestigating

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

2. 25 de mayo de 2026 a las 13:38 UTCinvestigating

   We are currently investigating this issue.

3. 25 de mayo de 2026 a las 14:10 UTCinvestigating

   We are continuing to investigate this issue.

4. 25 de mayo de 2026 a las 14:46 UTCidentified

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

5. 25 de mayo de 2026 a las 15:35 UTCidentified

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

6. 25 de mayo de 2026 a las 15:45 UTCmonitoring

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

7. 25 de mayo de 2026 a las 15:55 UTCresolved

   This incident has been resolved.

1. 6 de mayo de 2026 a las 15:40 UTCidentified

   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. 6 de mayo de 2026 a las 19:46 UTCidentified

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

3. 7 de mayo de 2026 a las 12:40 UTCmonitoring

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

4. 7 de mayo de 2026 a las 18:42 UTCresolved

   This incident has been resolved.

1. 17 de abril de 2026 a las 16:45 UTCidentified

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

2. 17 de abril de 2026 a las 17:05 UTCmonitoring

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

3. 17 de abril de 2026 a las 17:05 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 17 de abril de 2026 a las 17:15 UTCresolved

   This incident has been resolved.

1. 15 de abril de 2026 a las 13:40 UTCinvestigating

   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. 15 de abril de 2026 a las 13:42 UTCidentified

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

3. 15 de abril de 2026 a las 14:02 UTCmonitoring

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

4. 15 de abril de 2026 a las 15:34 UTCresolved

   This incident has been resolved.

1. 7 de abril de 2026 a las 17:30 UTCidentified

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

2. 7 de abril de 2026 a las 17:32 UTCmonitoring

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

3. 7 de abril de 2026 a las 17:42 UTCresolved

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

1. 19 de marzo de 2026 a las 18:43 UTCidentified

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

2. 19 de marzo de 2026 a las 18:53 UTCresolved

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

1. 13 de marzo de 2026 a las 11:29 UTCinvestigating

   We are currently investigating this issue.

2. 13 de marzo de 2026 a las 11:56 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 de marzo de 2026 a las 12:19 UTCidentified

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

4. 13 de marzo de 2026 a las 12:33 UTCmonitoring

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

5. 13 de marzo de 2026 a las 12:49 UTCresolved

   The incident has been resolved.

1. 25 de febrero de 2026 a las 19:10 UTCinvestigating

   We are currently investigating this issue.

2. 25 de febrero de 2026 a las 19:29 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 de febrero de 2026 a las 19:29 UTCidentified

   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. 25 de febrero de 2026 a las 20:25 UTCidentified

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

5. 25 de febrero de 2026 a las 21:36 UTCmonitoring

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

6. 25 de febrero de 2026 a las 21:45 UTCresolved

   This incident has been resolved.

1. 29 de noviembre de 2025 a las 8:38 UTCidentified

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

2. 29 de noviembre de 2025 a las 9:02 UTCidentified

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

3. 29 de noviembre de 2025 a las 9:56 UTCresolved

   This incident has been resolved.

1. 28 de noviembre de 2025 a las 16:30 UTCidentified

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

2. 28 de noviembre de 2025 a las 17:19 UTCmonitoring

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

3. 28 de noviembre de 2025 a las 17:56 UTCresolved

   Events are processing normally.