Mailjet の障害履歴

1. 2026年9月4日 12:23 UTCmonitoring

   マイクロソフトは、8:00 UTC を始め、すべての M365 地域における不正なメールの量が増えたという事件を経験し始めました。 影響を受ける応答は「451 4.7.500 Server」を返します。 当社のチームは、状況を積極的に監視しています。 他のメールプロバイダへの送信は影響を受けません.

2. 2026年9月4日 12:55 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月5日 10:01 UTCinvestigating

   We are currently investigating this issue.

2. 2026年6月5日 10:25 UTCidentified

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

3. 2026年6月5日 10:26 UTCmonitoring

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

4. 2026年6月5日 10:33 UTCresolved

   This incident has been resolved.

1. 2025年10月14日 13:30 UTCinvestigating

   Lag are identified we are investigating the issue

2. 2025年10月14日 14:01 UTCidentified

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

3. 2025年10月14日 15:52 UTCidentified

   The fix is under review.

4. 2025年10月14日 16:33 UTCidentified

   The fix is now under testing.

5. 2025年10月14日 18:57 UTCmonitoring

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

6. 2025年10月14日 20:13 UTCmonitoring

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

7. 2025年10月15日 3:42 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 2025年10月15日 3:42 UTCresolved

   This incident has been resolved.

1. 2025年10月2日 9:24 UTCinvestigating

   We are currently investigating this issue.

2. 2025年10月2日 9:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年10月2日 9:40 UTCidentified

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

4. 2025年10月2日 10:05 UTCmonitoring

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

5. 2025年10月2日 10:40 UTCresolved

   This incident has been resolved.

1. 2025年10月1日 8:12 UTCinvestigating

   We are currently investigating this issue.

2. 2025年10月1日 9:08 UTCmonitoring

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

3. 2025年10月1日 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. 2025年10月1日 11:15 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025年10月1日 20:30 UTCmonitoring

   We are continuing to actively monitor the system.

6. 2025年10月2日 0:42 UTCresolved

   This incident has been resolved.

1. 2025年9月30日 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. 2025年9月30日 10:36 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年9月30日 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. 2025年9月30日 16:09 UTCidentified

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

5. 2025年9月30日 17:44 UTCmonitoring

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

6. 2025年9月30日 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. 2025年9月4日 6:54 UTCinvestigating

   We are currently investigating this issue.

2. 2025年9月4日 8:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年9月4日 8:55 UTCidentified

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

4. 2025年9月4日 10:33 UTCidentified

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

5. 2025年9月4日 11:11 UTCmonitoring

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

6. 2025年9月4日 12:30 UTCresolved

   This incident has been resolved.

1. 2025年7月6日 9:07 UTCinvestigating

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

2. 2025年7月6日 9:11 UTCmonitoring

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

3. 2025年7月6日 9:26 UTCresolved

   This incident has been resolved.

1. 2025年1月31日 11:39 UTCinvestigating

   We are currently investigating this issue.

2. 2025年1月31日 12:09 UTCidentified

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

3. 2025年1月31日 13:46 UTCmonitoring

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

4. 2025年1月31日 14:05 UTCresolved

   This incident has been resolved.

1. 2024年10月23日 11:55 UTCinvestigating

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

2. 2024年10月23日 13:30 UTCidentified

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

3. 2024年10月23日 13:32 UTCmonitoring

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

4. 2024年10月23日 14:56 UTCresolved

   This incident has been resolved.

1. 2024年10月1日 12:24 UTCinvestigating

   We are currently investigating login issues on app

2. 2024年10月1日 12:38 UTCmonitoring

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

3. 2024年10月1日 15:08 UTCresolved

   This incident has been resolved.

1. 2024年7月31日 5:44 UTCidentified

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

2. 2024年7月31日 8:13 UTCidentified

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

3. 2024年7月31日 8:36 UTCmonitoring

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

4. 2024年7月31日 9: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. 2024年7月31日 10:51 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2024年7月31日 11:03 UTCresolved

   This incident has been resolved.

1. 2024年7月30日 12:25 UTCinvestigating

   We are currently investigating this issue.

2. 2024年7月30日 12:34 UTCidentified

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

3. 2024年7月30日 16:29 UTCidentified

   We are continuing to work through the fix for this issue

4. 2024年7月30日 19:06 UTCidentified

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

5. 2024年7月30日 22:05 UTCmonitoring

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

6. 2024年7月31日 1:55 UTCresolved

   The service is back to normal.

1. 2024年5月31日 8:07 UTCinvestigating

   We are currently investigating this issue.

2. 2024年5月31日 8:24 UTCidentified

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

3. 2024年5月31日 8:50 UTCmonitoring

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

4. 2024年5月31日 9:48 UTCresolved

   This incident has been resolved.

1. 2024年5月27日 15:54 UTCinvestigating

   We are currently investigating this issue.

2. 2024年5月27日 16:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024年5月27日 18:11 UTCresolved

   This incident has been resolved.

1. 2024年5月27日 13:23 UTCidentified

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

2. 2024年5月27日 13:48 UTCinvestigating

   We are currently investigating this issue.

3. 2024年5月27日 13:57 UTCmonitoring

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

4. 2024年5月27日 14:13 UTCresolved

   This incident has been resolved.

1. 2023年12月11日 15:23 UTCinvestigating

   We are currently investigating this issue.

2. 2023年12月11日 16:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 2023年12月11日 16:30 UTCidentified

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

4. 2023年12月11日 17:05 UTCmonitoring

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

5. 2023年12月11日 18:15 UTCmonitoring

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

6. 2023年12月11日 18:31 UTCmonitoring

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

7. 2023年12月11日 19:28 UTCresolved

   This incident has been resolved.

1. 2023年10月9日 10:12 UTCinvestigating

   We are currently investigating this issue.

2. 2023年10月9日 10:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 2023年10月9日 11:32 UTCidentified

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

4. 2023年10月9日 14:27 UTCmonitoring

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

5. 2023年10月9日 15:55 UTCresolved

   This incident has been resolved.

1. 2023年9月15日 3:00 UTCinvestigating

   Mailjet Engineering is investigating an email sending delay.

2. 2023年9月15日 4:25 UTCmonitoring

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

3. 2023年9月15日 4:40 UTCresolved

   This incident has been resolved.

1. 2023年6月28日 7:59 UTCinvestigating

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

2. 2023年6月28日 8:06 UTCidentified

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

3. 2023年6月28日 8: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. 2023年6月28日 9:25 UTCmonitoring

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

5. 2023年6月28日 9:52 UTCresolved

   This incident has been resolved.