Alertmedia 장애 기록

1. 2026년 9월 1일 PM 4:40 UTCidentified

   우리는 우리의 메시징 중 하나를 가진 문제점을 확인했습니다 (Twilio)는 플랫폼 (노화, 위협 경고, 사건 응답, 여행 위험 경고)에서 몇몇 SMS 메시지 및 음성 납품의 납품에 충격을 줍니다. 우리의 엔지니어링 팀은 투자 및 검토 충격 및 잠재적 완화입니다. 우리는 Twilio와 협력하여 문제를 모니터링합니다. Twilio의 상태 페이지: https://status.twilio.com/ SMS 메시지의 거친 10 %가 실패합니다.

2. 2026년 9월 1일 PM 5:20 UTCidentified

   우리는 Twilio와의 문제를 모니터링합니다. Voice Deliverability의 문제는 식별되어 수정이 배포됩니다. SMS 지연의 문제점은 확인되고 엔지니어는 고침에 작동됩니다. Twilio의 상태 페이지: https://status.twilio.com/

3. 2026년 9월 1일 PM 5:36 UTCmonitoring

   SMS 및 Voice에 대한 수정이 적용되어 오류율의 감소를 볼 수 있습니다. 음성과 SMS를 위한 기능 정상에 돌려보내는. 우리는 문제를 계속 모니터링 할 것입니다. Twilio의 상태 페이지: https://status.twilio.com/

4. 2026년 9월 1일 PM 6:26 UTCresolved

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

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

1. 2026년 6월 4일 PM 9:05 UTCinvestigating

   We are aware of some users experiencing issues with login in via mobile for both Android and iOS systems. The web app is working as expected. The team is investigating

2. 2026년 6월 4일 PM 11:11 UTCinvestigating

   We are continuing to investigate the issue

3. 2026년 6월 5일 AM 12:07 UTCidentified

   The issue has been identified and we are working to resolve this issue for customers as soon as possible

4. 2026년 6월 5일 AM 2:18 UTCmonitoring

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

5. 2026년 6월 5일 PM 2:19 UTCresolved

   This incident has been resolved.

1. 2026년 6월 3일 PM 7:14 UTCidentified

   We have identified an issue that is causing some user imports to fail under specific conditions and are working to implement a fix.

2. 2026년 6월 3일 PM 9:03 UTCmonitoring

   We are currently deploying a fix for this issue.

3. 2026년 6월 4일 AM 2:09 UTCresolved

   This incident has been resolved.

1. 2026년 1월 14일 PM 6:39 UTCmonitoring

   We are currently monitoring the ongoing issues with Verizon's (US) mobile network. SMS and Voice messages to Verizon phone numbers may be delayed or fail to deliver while these issues persist.

2. 2026년 1월 15일 AM 3:32 UTCresolved

   The outage is resolved, according to Verizon.

1. 2026년 1월 13일 PM 7:17 UTCinvestigating

   We are currently investigating reports of intermittent latency in the app and on login

2. 2026년 1월 13일 PM 7:46 UTCidentified

   The issue has been identified and we are working on a fix.

3. 2026년 1월 13일 PM 7:58 UTCmonitoring

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

4. 2026년 1월 13일 PM 8:31 UTCresolved

   This incident has been resolved

1. 2025년 12월 2일 PM 5:17 UTCinvestigating

   We are investigating an incident that is preventing users from logging in.

2. 2025년 12월 2일 PM 5:27 UTCmonitoring

   Systems are back to normal, users should be able to login. We are monitoring the issue

3. 2025년 12월 2일 PM 5:46 UTCresolved

   This incident has been resolved.

1. 2025년 11월 18일 PM 6:03 UTCidentified

   We have identified an issue when attempting to load the Threat History and Safety maps in our dashboard and are working on a fix.

2. 2025년 11월 18일 PM 10:42 UTCresolved

   A fix has been implemented and we are monitoring the results. Both Threat History and Safety Maps are responsive.

1. 2025년 11월 14일 PM 8:04 UTCinvestigating

   We’re currently investigating reports of SFTP upload failures affecting some customers. Our engineering team is investigating the issue.

2. 2025년 11월 15일 AM 12:59 UTCmonitoring

   A fix has been applied and we are monitoring the environment.

3. 2025년 11월 15일 AM 2:27 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 AM 9:46 UTCidentified

   AWS services are recovering and we are mitigating impact where possible. The service responsible for notification sends is degraded, delaying notifications, threat warnings, and incident response tasks.

2. 2025년 10월 20일 AM 10:05 UTCidentified

   Notification sends are processing. Recovery in progress.

3. 2025년 10월 20일 AM 10:05 UTCidentified

   Updated impacted components

4. 2025년 10월 20일 AM 11:50 UTCidentified

   Notification sends and threat warnings are operational. FTP imports are not currently processing.

5. 2025년 10월 20일 PM 12:34 UTCidentified

   FTP imports are not currently processing. Employee Safety Monitoring is down.

6. 2025년 10월 20일 PM 12:55 UTCidentified

   FTP imports are operational in the NA2 production environment. They are not processing in the NA1 production environment.

7. 2025년 10월 20일 PM 3:24 UTCidentified

   FTP Imports are not processing in either environment

8. 2025년 10월 20일 PM 5:56 UTCidentified

   We are experiencing delayed notifications due to downstream providers. FTP Import performance is still degraded for both environments

9. 2025년 10월 20일 PM 6:51 UTCidentified

   There remain issues related to SFTP (AWS Transfer Family Service) that are still causing import issues.

10. 2025년 10월 20일 PM 8:08 UTCmonitoring

    We are continuing to see delays in sending Threat Warnings

11. 2025년 10월 20일 PM 9:00 UTCmonitoring

    Threat Warnings are operational and we are continuing to monitor the situation for Imports

12. 2025년 10월 20일 PM 9:04 UTCmonitoring

    All systems are back to operational status. We will continue monitor the situation.

13. 2025년 10월 21일 AM 9:09 UTCresolved

    This incident has been resolved.

1. 2025년 9월 26일 PM 3:02 UTCinvestigating

   Escalation messages are unable to send for some customers. All other message types are able to send. Our team is investigating the issue.

2. 2025년 9월 26일 PM 3:22 UTCidentified

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

3. 2025년 9월 26일 PM 5:16 UTCmonitoring

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

4. 2025년 9월 26일 PM 5:31 UTCresolved

   The incident has been resolved. Escalations function as expected for all customers.

1. 2025년 5월 13일 PM 9:03 UTCmonitoring

   Threat warnings are degraded for some customers and we are working to restore full service. Some threat warnings were not delivered due to missing data during processing. We’ve identified the issue and are actively backfilling the data to ensure alerts are complete and accurate. Full restoration will take a few hours.

2. 2025년 5월 13일 PM 10:04 UTCresolved

   Threat warnings are degraded for some customers and we are working to restore full service. Some threat warnings were not delivered due to missing data during processing. We’ve identified the issue and are actively backfilling the data to ensure alerts are complete and accurate. Full restoration will take a few hours.

1. 2025년 5월 13일 PM 10:18 UTCmonitoring

   Threat warnings are degraded for some customers and we are working to restore full service. Some threat warnings were not delivered due to missing data during processing. We’ve identified the issue and are actively backfilling the data to ensure alerts are complete and accurate. Full restoration will take a few hours.

2. 2025년 5월 14일 PM 3:08 UTCmonitoring

   The backfill of the data is almost complete. Full threat warning coverage has been restored for the majority of customers.

3. 2025년 5월 14일 PM 7:56 UTCresolved

   The backfill process has completed and full threat warning coverage has been restored for all customers.

1. 2025년 3월 26일 PM 10:06 UTCidentified

   We have identified an issue that is preventing some users from being able to log in and are working on a fix.

2. 2025년 3월 26일 PM 10:17 UTCresolved

   This issue has been resolved and all users should be able to log in as normal.

1. 2025년 3월 11일 PM 5:49 UTCinvestigating

   We are currently investigating an issue that is causing some users to be unable to access the AlertMedia Dashboard.

2. 2025년 3월 11일 PM 6:19 UTCmonitoring

   We are monitoring the issue, services are restored.

3. 2025년 3월 11일 PM 6:58 UTCresolved

   This incident has been resolved.

1. 2025년 2월 20일 PM 7:31 UTCinvestigating

   We are currently investigating an issue that is causing user import via SFTP to be inaccessible for some customers.

2. 2025년 2월 20일 PM 7:37 UTCmonitoring

   We have implemented a fix for the SFTP issues we were experiencing and are monitoring the system as performance improves.

3. 2025년 2월 20일 PM 7:56 UTCresolved

   This incident has been resolved.

1. 2025년 2월 13일 PM 4:03 UTCinvestigating

   We are currently investigating an issue that is causing slowness in the AlertMedia systems

2. 2025년 2월 13일 PM 4:19 UTCmonitoring

   The system should be coming back to normal performance levels. We are continuing to investigate the issue

3. 2025년 2월 13일 PM 6:36 UTCresolved

   The incident has been resolved, all systems should be running as expected.

1. 2025년 1월 28일 PM 1:50 UTCinvestigating

   We are currently investigating an issue that is causing some voice notifications and incoming calls to Emergency Lines to fail.

2. 2025년 1월 28일 PM 2:11 UTCidentified

   We have identified the issue causing some voice notifications and incoming calls to Emergency Lines to fail and are working with our partners to resolve the issue.

3. 2025년 1월 28일 PM 2:58 UTCresolved

   This incident has been resolved. Voice notifications and incoming calls to Emergency lines have returned to normal.

1. 2024년 11월 13일 PM 1:29 UTCmonitoring

   Users are experiencing intermittent delays in loading map layers. The root cause is performance issues with the ArcGIS service (see https://status.arcgis.com/). We are monitoring the issue.

2. 2024년 11월 13일 PM 2:37 UTCresolved

   We are seeing recovery of our Visual Intelligence systems as ArcGIS reports the issue on their end has stabilized.

1. 2024년 9월 26일 PM 5:27 UTCinvestigating

   We are currently investigating an issue that is causing users to be unable to access the AlertMedia Dashboard.

2. 2024년 9월 26일 PM 5:38 UTCmonitoring

   The AlertMedia dashboard has returned to a healthy operational state. We will continue to monitor the fix in place to ensure continued performance.

3. 2024년 9월 26일 PM 5:53 UTCresolved

   This incident has been resolved.

1. 2024년 4월 19일 PM 6:12 UTCinvestigating

   We are investigating an issue with Imports and group updates.

2. 2024년 4월 19일 PM 6:52 UTCidentified

   The issue has been identified and we are working on a fix

3. 2024년 4월 19일 PM 8:09 UTCidentified

   We are continuing to work on implementing the fix for ongoing performance issues with imports.

4. 2024년 4월 19일 PM 8:41 UTCmonitoring

   The fix has been deployed to production, and we're seeing the system recover. We will continue to monitor and update this page once all systems are confirmed to be recovered and stable.

5. 2024년 4월 19일 PM 9:00 UTCresolved

   This incident has been resolved.