Alertmedia 中断历史

1. 2026年9月1日 UTC 16:40identified

   我们与我们的一个信息发送提供商(Twilio)确定了一个问题,即影响从平台发送一些短信和语音发送(通知、威胁警告、事件应对、旅行风险警告)。 我们的工程小组正在调查和审查影响和可能的缓解措施。 我们正在同Twilio合作监测这一问题。 Twilio的地位页面:https://status.twilio.com/ (中文(简体) ). 大约10%的短信失败了.

2. 2026年9月1日 UTC 17:20identified

   我们继续与Twilio一起监测这一问题。 语音可交付性问题已经确定,正在部署一个解决方案。 短信延迟的问题已经查明,工程师们正在设法解决。 Twilio的地位页面:https://status.twilio.com/ (中文(简体) )

3. 2026年9月1日 UTC 17:36monitoring

   已经为短消息和语音应用了修复系统,我们开始看到错误率下降。 语音和短信功能恢复正常。 我们将继续监测这一问题。 Twilio的地位页面:https://status.twilio.com/ (中文(简体) )

4. 2026年9月1日 UTC 18:26resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月4日 UTC 21:05investigating

   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日 UTC 23:11investigating

   We are continuing to investigate the issue

3. 2026年6月5日 UTC 00:07identified

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

4. 2026年6月5日 UTC 02:18monitoring

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

5. 2026年6月5日 UTC 14:19resolved

   This incident has been resolved.

1. 2026年6月3日 UTC 19:14identified

   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日 UTC 21:03monitoring

   We are currently deploying a fix for this issue.

3. 2026年6月4日 UTC 02:09resolved

   This incident has been resolved.

1. 2026年1月14日 UTC 18:39monitoring

   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日 UTC 03:32resolved

   The outage is resolved, according to Verizon.

1. 2026年1月13日 UTC 19:17investigating

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

2. 2026年1月13日 UTC 19:46identified

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

3. 2026年1月13日 UTC 19:58monitoring

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

4. 2026年1月13日 UTC 20:31resolved

   This incident has been resolved

1. 2025年12月2日 UTC 17:17investigating

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

2. 2025年12月2日 UTC 17:27monitoring

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

3. 2025年12月2日 UTC 17:46resolved

   This incident has been resolved.

1. 2025年11月18日 UTC 18:03identified

   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日 UTC 22:42resolved

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

1. 2025年11月14日 UTC 20:04investigating

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

2. 2025年11月15日 UTC 00:59monitoring

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

3. 2025年11月15日 UTC 02:27resolved

   This incident has been resolved.

1. 2025年10月20日 UTC 09:46identified

   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日 UTC 10:05identified

   Notification sends are processing. Recovery in progress.

3. 2025年10月20日 UTC 10:05identified

   Updated impacted components

4. 2025年10月20日 UTC 11:50identified

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

5. 2025年10月20日 UTC 12:34identified

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

6. 2025年10月20日 UTC 12:55identified

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

7. 2025年10月20日 UTC 15:24identified

   FTP Imports are not processing in either environment

8. 2025年10月20日 UTC 17:56identified

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

9. 2025年10月20日 UTC 18:51identified

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

10. 2025年10月20日 UTC 20:08monitoring

    We are continuing to see delays in sending Threat Warnings

11. 2025年10月20日 UTC 21:00monitoring

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

12. 2025年10月20日 UTC 21:04monitoring

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

13. 2025年10月21日 UTC 09:09resolved

    This incident has been resolved.

1. 2025年9月26日 UTC 15:02investigating

   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日 UTC 15:22identified

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

3. 2025年9月26日 UTC 17:16monitoring

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

4. 2025年9月26日 UTC 17:31resolved

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

1. 2025年5月13日 UTC 21:03monitoring

   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日 UTC 22:04resolved

   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日 UTC 22:18monitoring

   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日 UTC 15:08monitoring

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

3. 2025年5月14日 UTC 19:56resolved

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

1. 2025年3月26日 UTC 22:06identified

   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日 UTC 22:17resolved

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

1. 2025年3月11日 UTC 17:49investigating

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

2. 2025年3月11日 UTC 18:19monitoring

   We are monitoring the issue, services are restored.

3. 2025年3月11日 UTC 18:58resolved

   This incident has been resolved.

1. 2025年2月20日 UTC 19:31investigating

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

2. 2025年2月20日 UTC 19:37monitoring

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

3. 2025年2月20日 UTC 19:56resolved

   This incident has been resolved.

1. 2025年2月13日 UTC 16:03investigating

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

2. 2025年2月13日 UTC 16:19monitoring

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

3. 2025年2月13日 UTC 18:36resolved

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

1. 2025年1月28日 UTC 13:50investigating

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

2. 2025年1月28日 UTC 14:11identified

   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日 UTC 14:58resolved

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

1. 2024年11月13日 UTC 13:29monitoring

   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日 UTC 14:37resolved

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

1. 2024年9月26日 UTC 17:27investigating

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

2. 2024年9月26日 UTC 17:38monitoring

   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日 UTC 17:53resolved

   This incident has been resolved.

1. 2024年4月19日 UTC 18:12investigating

   We are investigating an issue with Imports and group updates.

2. 2024年4月19日 UTC 18:52identified

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

3. 2024年4月19日 UTC 20:09identified

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

4. 2024年4月19日 UTC 20:41monitoring

   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日 UTC 21:00resolved

   This incident has been resolved.