Mailjet 장애 기록

1. 2026년 9월 4일 PM 12:23 UTCmonitoring

   08:00 UTC를 시작으로 Microsoft는 모든 M365 지역에 걸쳐 번거로운 이메일의 증가 된 볼륨을 유발하는 사건을 경험했습니다. 영향을받는 응답은 "451 4.7.500 서버 바쁜"로 돌아갑니다. 우리 팀은 적극적으로 상황을 모니터링하고 있습니다. 다른 이메일 공급자에게 보내는 것은 영향을 미치지 않습니다.

2. 2026년 9월 4일 PM 12:55 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 5일 AM 10:01 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 6월 5일 AM 10:25 UTCidentified

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

3. 2026년 6월 5일 AM 10:26 UTCmonitoring

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

4. 2026년 6월 5일 AM 10:33 UTCresolved

   This incident has been resolved.

1. 2025년 10월 14일 PM 1:30 UTCinvestigating

   Lag are identified we are investigating the issue

2. 2025년 10월 14일 PM 2:01 UTCidentified

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

3. 2025년 10월 14일 PM 3:52 UTCidentified

   The fix is under review.

4. 2025년 10월 14일 PM 4:33 UTCidentified

   The fix is now under testing.

5. 2025년 10월 14일 PM 6:57 UTCmonitoring

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

6. 2025년 10월 14일 PM 8:13 UTCmonitoring

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

7. 2025년 10월 15일 AM 3:42 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 2025년 10월 15일 AM 3:42 UTCresolved

   This incident has been resolved.

1. 2025년 10월 2일 AM 9:24 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 10월 2일 AM 9:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 10월 2일 AM 9:40 UTCidentified

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

4. 2025년 10월 2일 AM 10:05 UTCmonitoring

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

5. 2025년 10월 2일 AM 10:40 UTCresolved

   This incident has been resolved.

1. 2025년 10월 1일 AM 8:12 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 10월 1일 AM 9:08 UTCmonitoring

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

3. 2025년 10월 1일 AM 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일 AM 11:15 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025년 10월 1일 PM 8:30 UTCmonitoring

   We are continuing to actively monitor the system.

6. 2025년 10월 2일 AM 12:42 UTCresolved

   This incident has been resolved.

1. 2025년 9월 30일 AM 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일 AM 10:36 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 9월 30일 AM 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일 PM 4:09 UTCidentified

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

5. 2025년 9월 30일 PM 5:44 UTCmonitoring

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

6. 2025년 9월 30일 PM 6: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일 AM 6:54 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 9월 4일 AM 8:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 9월 4일 AM 8:55 UTCidentified

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

4. 2025년 9월 4일 AM 10:33 UTCidentified

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

5. 2025년 9월 4일 AM 11:11 UTCmonitoring

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

6. 2025년 9월 4일 PM 12:30 UTCresolved

   This incident has been resolved.

1. 2025년 7월 6일 AM 9:07 UTCinvestigating

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

2. 2025년 7월 6일 AM 9:11 UTCmonitoring

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

3. 2025년 7월 6일 AM 9:26 UTCresolved

   This incident has been resolved.

1. 2025년 1월 31일 AM 11:39 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 1월 31일 PM 12:09 UTCidentified

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

3. 2025년 1월 31일 PM 1:46 UTCmonitoring

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

4. 2025년 1월 31일 PM 2:05 UTCresolved

   This incident has been resolved.

1. 2024년 10월 23일 AM 11:55 UTCinvestigating

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

2. 2024년 10월 23일 PM 1:30 UTCidentified

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

3. 2024년 10월 23일 PM 1:32 UTCmonitoring

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

4. 2024년 10월 23일 PM 2:56 UTCresolved

   This incident has been resolved.

1. 2024년 10월 1일 PM 12:24 UTCinvestigating

   We are currently investigating login issues on app

2. 2024년 10월 1일 PM 12:38 UTCmonitoring

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

3. 2024년 10월 1일 PM 3:08 UTCresolved

   This incident has been resolved.

1. 2024년 7월 31일 AM 5:44 UTCidentified

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

2. 2024년 7월 31일 AM 8:13 UTCidentified

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

3. 2024년 7월 31일 AM 8:36 UTCmonitoring

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

4. 2024년 7월 31일 AM 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일 AM 10:51 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2024년 7월 31일 AM 11:03 UTCresolved

   This incident has been resolved.

1. 2024년 7월 30일 PM 12:25 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 7월 30일 PM 12:34 UTCidentified

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

3. 2024년 7월 30일 PM 4:29 UTCidentified

   We are continuing to work through the fix for this issue

4. 2024년 7월 30일 PM 7:06 UTCidentified

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

5. 2024년 7월 30일 PM 10: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일 AM 1:55 UTCresolved

   The service is back to normal.

1. 2024년 5월 31일 AM 8:07 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 5월 31일 AM 8:24 UTCidentified

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

3. 2024년 5월 31일 AM 8:50 UTCmonitoring

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

4. 2024년 5월 31일 AM 9:48 UTCresolved

   This incident has been resolved.

1. 2024년 5월 27일 PM 3:54 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 5월 27일 PM 4:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 5월 27일 PM 6:11 UTCresolved

   This incident has been resolved.

1. 2024년 5월 27일 PM 1:23 UTCidentified

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

2. 2024년 5월 27일 PM 1:48 UTCinvestigating

   We are currently investigating this issue.

3. 2024년 5월 27일 PM 1:57 UTCmonitoring

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

4. 2024년 5월 27일 PM 2:13 UTCresolved

   This incident has been resolved.

1. 2023년 12월 11일 PM 3:23 UTCinvestigating

   We are currently investigating this issue.

2. 2023년 12월 11일 PM 4:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 2023년 12월 11일 PM 4:30 UTCidentified

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

4. 2023년 12월 11일 PM 5:05 UTCmonitoring

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

5. 2023년 12월 11일 PM 6:15 UTCmonitoring

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

6. 2023년 12월 11일 PM 6:31 UTCmonitoring

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

7. 2023년 12월 11일 PM 7:28 UTCresolved

   This incident has been resolved.

1. 2023년 10월 9일 AM 10:12 UTCinvestigating

   We are currently investigating this issue.

2. 2023년 10월 9일 AM 10:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 2023년 10월 9일 AM 11:32 UTCidentified

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

4. 2023년 10월 9일 PM 2:27 UTCmonitoring

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

5. 2023년 10월 9일 PM 3:55 UTCresolved

   This incident has been resolved.

1. 2023년 9월 15일 AM 3:00 UTCinvestigating

   Mailjet Engineering is investigating an email sending delay.

2. 2023년 9월 15일 AM 4:25 UTCmonitoring

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

3. 2023년 9월 15일 AM 4:40 UTCresolved

   This incident has been resolved.

1. 2023년 6월 28일 AM 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일 AM 8:06 UTCidentified

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

3. 2023년 6월 28일 AM 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일 AM 9:25 UTCmonitoring

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

5. 2023년 6월 28일 AM 9:52 UTCresolved

   This incident has been resolved.