Historique des pannes de Mailjet

1. 4 septembre 2026 à 12:23 UTCmonitoring

   À partir de 08:00 UTC, Microsoft a commencé à vivre un incident provoquant un volume accru de courriels différés dans toutes les régions du M365. Les réponses touchées retournent « 451 4.7.500 Serveur occupé ». Nos équipes surveillent activement la situation. L'envoi à d'autres fournisseurs de courriels n'est pas affecté.

2. 4 septembre 2026 à 12:55 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 5 juin 2026 à 10:01 UTCinvestigating

   We are currently investigating this issue.

2. 5 juin 2026 à 10:25 UTCidentified

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

3. 5 juin 2026 à 10:26 UTCmonitoring

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

4. 5 juin 2026 à 10:33 UTCresolved

   This incident has been resolved.

1. 14 octobre 2025 à 13:30 UTCinvestigating

   Lag are identified we are investigating the issue

2. 14 octobre 2025 à 14:01 UTCidentified

   The issue has been identified and our team is working on a fix.

3. 14 octobre 2025 à 15:52 UTCidentified

   The fix is under review.

4. 14 octobre 2025 à 16:33 UTCidentified

   The fix is now under testing.

5. 14 octobre 2025 à 18:57 UTCmonitoring

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

6. 14 octobre 2025 à 20:13 UTCmonitoring

   We'll be monitoring the situation throughout the night until 9am CET to ensure stable service delivery.

7. 15 octobre 2025 à 03:42 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 15 octobre 2025 à 03:42 UTCresolved

   This incident has been resolved.

1. 2 octobre 2025 à 09:24 UTCinvestigating

   We are currently investigating this issue.

2. 2 octobre 2025 à 09:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 octobre 2025 à 09:40 UTCidentified

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

4. 2 octobre 2025 à 10:05 UTCmonitoring

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

5. 2 octobre 2025 à 10:40 UTCresolved

   This incident has been resolved.

1. 1 octobre 2025 à 08:12 UTCinvestigating

   We are currently investigating this issue.

2. 1 octobre 2025 à 09:08 UTCmonitoring

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

3. 1 octobre 2025 à 10:56 UTCmonitoring

   We are continuing to monitor for any further issues. Events are being processed and the service is catching up on missing events.

4. 1 octobre 2025 à 11:15 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 1 octobre 2025 à 20:30 UTCmonitoring

   We are continuing to actively monitor the system.

6. 2 octobre 2025 à 00:42 UTCresolved

   This incident has been resolved.

1. 30 septembre 2025 à 10:21 UTCinvestigating

   We are currently investigating an issue impacting email processing along with app.mailjet.com login issues, reflecting into "wrong password" errors.

2. 30 septembre 2025 à 10:36 UTCinvestigating

   We are continuing to investigate this issue.

3. 30 septembre 2025 à 11:12 UTCidentified

   We have identified the root cause of the issue. While we are working on getting this resolved, clients will experience inability to log into app.mailjet.com as well as experience email processing delays.

4. 30 septembre 2025 à 16:09 UTCidentified

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

5. 30 septembre 2025 à 17:44 UTCmonitoring

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

6. 30 septembre 2025 à 18:05 UTCresolved

   The incident has been resolved. Any missing statistics during the incident haven't been lost and will show up in the statistics page later today.

1. 4 septembre 2025 à 06:54 UTCinvestigating

   We are currently investigating this issue.

2. 4 septembre 2025 à 08:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 septembre 2025 à 08:55 UTCidentified

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

4. 4 septembre 2025 à 10:33 UTCidentified

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

5. 4 septembre 2025 à 11:11 UTCmonitoring

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

6. 4 septembre 2025 à 12:30 UTCresolved

   This incident has been resolved.

1. 6 juillet 2025 à 09:07 UTCinvestigating

   Our team is currently investigating a potential issue impacting some customers on webhook connection.

2. 6 juillet 2025 à 09:11 UTCmonitoring

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

3. 6 juillet 2025 à 09:26 UTCresolved

   This incident has been resolved.

1. 31 janvier 2025 à 11:39 UTCinvestigating

   We are currently investigating this issue.

2. 31 janvier 2025 à 12:09 UTCidentified

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

3. 31 janvier 2025 à 13:46 UTCmonitoring

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

4. 31 janvier 2025 à 14:05 UTCresolved

   This incident has been resolved.

1. 23 octobre 2024 à 11:55 UTCinvestigating

   We are currently investigating issues with our Event API partially sending events.

2. 23 octobre 2024 à 13:30 UTCidentified

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

3. 23 octobre 2024 à 13:32 UTCmonitoring

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

4. 23 octobre 2024 à 14:56 UTCresolved

   This incident has been resolved.

1. 1 octobre 2024 à 12:24 UTCinvestigating

   We are currently investigating login issues on app

2. 1 octobre 2024 à 12:38 UTCmonitoring

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

3. 1 octobre 2024 à 15:08 UTCresolved

   This incident has been resolved.

1. 31 juillet 2024 à 05:44 UTCidentified

   The issue has been identified and we are currently working through the fix

2. 31 juillet 2024 à 08:13 UTCidentified

   The mitigation of the DDoS attack to our application is still in progress.

3. 31 juillet 2024 à 08:36 UTCmonitoring

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

4. 31 juillet 2024 à 09:17 UTCmonitoring

   We have implemented measures to mitigate the DDoS attack on our application and are continuously making adjustments to better withstand the attack. Some customers may report intermittent periods where the application experiences slowness or becomes unresponsive.

5. 31 juillet 2024 à 10:51 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 31 juillet 2024 à 11:03 UTCresolved

   This incident has been resolved.

1. 30 juillet 2024 à 12:25 UTCinvestigating

   We are currently investigating this issue.

2. 30 juillet 2024 à 12:34 UTCidentified

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

3. 30 juillet 2024 à 16:29 UTCidentified

   We are continuing to work through the fix for this issue

4. 30 juillet 2024 à 19:06 UTCidentified

   The mitigation of the DDoS attack to our application is still in progress.

5. 30 juillet 2024 à 22:05 UTCmonitoring

   The service is back but we're continuing to monitor its state to ensure there's no further issues.

6. 31 juillet 2024 à 01:55 UTCresolved

   The service is back to normal.

1. 31 mai 2024 à 08:07 UTCinvestigating

   We are currently investigating this issue.

2. 31 mai 2024 à 08:24 UTCidentified

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

3. 31 mai 2024 à 08:50 UTCmonitoring

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

4. 31 mai 2024 à 09:48 UTCresolved

   This incident has been resolved.

1. 27 mai 2024 à 15:54 UTCinvestigating

   We are currently investigating this issue.

2. 27 mai 2024 à 16:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 mai 2024 à 18:11 UTCresolved

   This incident has been resolved.

1. 27 mai 2024 à 13:23 UTCidentified

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

2. 27 mai 2024 à 13:48 UTCinvestigating

   We are currently investigating this issue.

3. 27 mai 2024 à 13:57 UTCmonitoring

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

4. 27 mai 2024 à 14:13 UTCresolved

   This incident has been resolved.

1. 11 décembre 2023 à 15:23 UTCinvestigating

   We are currently investigating this issue.

2. 11 décembre 2023 à 16:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 décembre 2023 à 16:30 UTCidentified

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

4. 11 décembre 2023 à 17:05 UTCmonitoring

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

5. 11 décembre 2023 à 18:15 UTCmonitoring

   Different fixes are being implemented and we are monitoring the results.

6. 11 décembre 2023 à 18:31 UTCmonitoring

   Remediation is still in progress and outbound mail continues to be delayed.

7. 11 décembre 2023 à 19:28 UTCresolved

   This incident has been resolved.

1. 9 octobre 2023 à 10:12 UTCinvestigating

   We are currently investigating this issue.

2. 9 octobre 2023 à 10:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 octobre 2023 à 11:32 UTCidentified

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

4. 9 octobre 2023 à 14:27 UTCmonitoring

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

5. 9 octobre 2023 à 15:55 UTCresolved

   This incident has been resolved.

1. 15 septembre 2023 à 03:00 UTCinvestigating

   Mailjet Engineering is investigating an email sending delay.

2. 15 septembre 2023 à 04:25 UTCmonitoring

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

3. 15 septembre 2023 à 04:40 UTCresolved

   This incident has been resolved.

1. 28 juin 2023 à 07:59 UTCinvestigating

   Some customers may report that scheduled campaigns are not being sent. Our teams are currently investigating this issue.

2. 28 juin 2023 à 08:06 UTCidentified

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

3. 28 juin 2023 à 08:47 UTCidentified

   Some customers may report degraded performance on sending campaigns or campaigns scheduled not being sent. Our teams are currently investigating this issue.

4. 28 juin 2023 à 09:25 UTCmonitoring

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

5. 28 juin 2023 à 09:52 UTCresolved

   This incident has been resolved.