История сбоев Mailjet

1. 4 сентября 2026 г. в 12:23 UTCmonitoring

   Начиная примерно с 08:00 UTC, Microsoft начала испытывать инцидент, вызвавший увеличение объема отложенных электронных писем во всех регионах M365. Затронутые ответы возвращают "451 4.7.500 Сервер занят". Наши команды активно следят за ситуацией. Отправка другим поставщикам электронной почты не затрагивается.

2. 4 сентября 2026 г. в 12:55 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 5 июня 2026 г. в 10:01 UTCinvestigating

   We are currently investigating this issue.

2. 5 июня 2026 г. в 10:25 UTCidentified

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

3. 5 июня 2026 г. в 10:26 UTCmonitoring

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

4. 5 июня 2026 г. в 10:33 UTCresolved

   This incident has been resolved.

1. 14 октября 2025 г. в 13:30 UTCinvestigating

   Lag are identified we are investigating the issue

2. 14 октября 2025 г. в 14:01 UTCidentified

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

3. 14 октября 2025 г. в 15:52 UTCidentified

   The fix is under review.

4. 14 октября 2025 г. в 16:33 UTCidentified

   The fix is now under testing.

5. 14 октября 2025 г. в 18:57 UTCmonitoring

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

6. 14 октября 2025 г. в 20:13 UTCmonitoring

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

7. 15 октября 2025 г. в 03:42 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 15 октября 2025 г. в 03:42 UTCresolved

   This incident has been resolved.

1. 2 октября 2025 г. в 09:24 UTCinvestigating

   We are currently investigating this issue.

2. 2 октября 2025 г. в 09:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 октября 2025 г. в 09:40 UTCidentified

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

4. 2 октября 2025 г. в 10:05 UTCmonitoring

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

5. 2 октября 2025 г. в 10:40 UTCresolved

   This incident has been resolved.

1. 1 октября 2025 г. в 08:12 UTCinvestigating

   We are currently investigating this issue.

2. 1 октября 2025 г. в 09:08 UTCmonitoring

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

3. 1 октября 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 октября 2025 г. в 11:15 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 1 октября 2025 г. в 20:30 UTCmonitoring

   We are continuing to actively monitor the system.

6. 2 октября 2025 г. в 00:42 UTCresolved

   This incident has been resolved.

1. 30 сентября 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 сентября 2025 г. в 10:36 UTCinvestigating

   We are continuing to investigate this issue.

3. 30 сентября 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 сентября 2025 г. в 16:09 UTCidentified

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

5. 30 сентября 2025 г. в 17:44 UTCmonitoring

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

6. 30 сентября 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 сентября 2025 г. в 06:54 UTCinvestigating

   We are currently investigating this issue.

2. 4 сентября 2025 г. в 08:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 сентября 2025 г. в 08:55 UTCidentified

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

4. 4 сентября 2025 г. в 10:33 UTCidentified

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

5. 4 сентября 2025 г. в 11:11 UTCmonitoring

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

6. 4 сентября 2025 г. в 12:30 UTCresolved

   This incident has been resolved.

1. 6 июля 2025 г. в 09:07 UTCinvestigating

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

2. 6 июля 2025 г. в 09:11 UTCmonitoring

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

3. 6 июля 2025 г. в 09:26 UTCresolved

   This incident has been resolved.

1. 31 января 2025 г. в 11:39 UTCinvestigating

   We are currently investigating this issue.

2. 31 января 2025 г. в 12:09 UTCidentified

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

3. 31 января 2025 г. в 13:46 UTCmonitoring

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

4. 31 января 2025 г. в 14:05 UTCresolved

   This incident has been resolved.

1. 23 октября 2024 г. в 11:55 UTCinvestigating

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

2. 23 октября 2024 г. в 13:30 UTCidentified

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

3. 23 октября 2024 г. в 13:32 UTCmonitoring

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

4. 23 октября 2024 г. в 14:56 UTCresolved

   This incident has been resolved.

1. 1 октября 2024 г. в 12:24 UTCinvestigating

   We are currently investigating login issues on app

2. 1 октября 2024 г. в 12:38 UTCmonitoring

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

3. 1 октября 2024 г. в 15:08 UTCresolved

   This incident has been resolved.

1. 31 июля 2024 г. в 05:44 UTCidentified

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

2. 31 июля 2024 г. в 08:13 UTCidentified

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

3. 31 июля 2024 г. в 08:36 UTCmonitoring

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

4. 31 июля 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 июля 2024 г. в 10:51 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 31 июля 2024 г. в 11:03 UTCresolved

   This incident has been resolved.

1. 30 июля 2024 г. в 12:25 UTCinvestigating

   We are currently investigating this issue.

2. 30 июля 2024 г. в 12:34 UTCidentified

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

3. 30 июля 2024 г. в 16:29 UTCidentified

   We are continuing to work through the fix for this issue

4. 30 июля 2024 г. в 19:06 UTCidentified

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

5. 30 июля 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 июля 2024 г. в 01:55 UTCresolved

   The service is back to normal.

1. 31 мая 2024 г. в 08:07 UTCinvestigating

   We are currently investigating this issue.

2. 31 мая 2024 г. в 08:24 UTCidentified

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

3. 31 мая 2024 г. в 08:50 UTCmonitoring

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

4. 31 мая 2024 г. в 09:48 UTCresolved

   This incident has been resolved.

1. 27 мая 2024 г. в 15:54 UTCinvestigating

   We are currently investigating this issue.

2. 27 мая 2024 г. в 16:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 мая 2024 г. в 18:11 UTCresolved

   This incident has been resolved.

1. 27 мая 2024 г. в 13:23 UTCidentified

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

2. 27 мая 2024 г. в 13:48 UTCinvestigating

   We are currently investigating this issue.

3. 27 мая 2024 г. в 13:57 UTCmonitoring

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

4. 27 мая 2024 г. в 14:13 UTCresolved

   This incident has been resolved.

1. 11 декабря 2023 г. в 15:23 UTCinvestigating

   We are currently investigating this issue.

2. 11 декабря 2023 г. в 16:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 декабря 2023 г. в 16:30 UTCidentified

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

4. 11 декабря 2023 г. в 17:05 UTCmonitoring

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

5. 11 декабря 2023 г. в 18:15 UTCmonitoring

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

6. 11 декабря 2023 г. в 18:31 UTCmonitoring

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

7. 11 декабря 2023 г. в 19:28 UTCresolved

   This incident has been resolved.

1. 9 октября 2023 г. в 10:12 UTCinvestigating

   We are currently investigating this issue.

2. 9 октября 2023 г. в 10:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 октября 2023 г. в 11:32 UTCidentified

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

4. 9 октября 2023 г. в 14:27 UTCmonitoring

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

5. 9 октября 2023 г. в 15:55 UTCresolved

   This incident has been resolved.

1. 15 сентября 2023 г. в 03:00 UTCinvestigating

   Mailjet Engineering is investigating an email sending delay.

2. 15 сентября 2023 г. в 04:25 UTCmonitoring

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

3. 15 сентября 2023 г. в 04:40 UTCresolved

   This incident has been resolved.

1. 28 июня 2023 г. в 07:59 UTCinvestigating

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

2. 28 июня 2023 г. в 08:06 UTCidentified

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

3. 28 июня 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 июня 2023 г. в 09:25 UTCmonitoring

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

5. 28 июня 2023 г. в 09:52 UTCresolved

   This incident has been resolved.