Störungsverlauf von Alertmedia

1. 23. Oktober 2026 um 20:38 UTCidentified

   Auswirkungen - iPhone-Benutzer, die das neueste Update der AlertMedia-App installiert haben (veröffentlicht am 22. Oktober), können die App nicht öffnen. Es schließt direkt nach dem Start. Die Android App ist nicht betroffen. iPhone-Benutzer, die das neueste App-Update nicht installiert haben, sind nicht betroffen. - Benachrichtigungen per SMS, E-Mail und Stimme werden immer noch zugestellt. Wir haben das Problem behoben und Apple um eine beschleunigte Überprüfung gebeten, und wir werden hier ein Update veröffentlichen, sobald der Fix im App Store ist. Was Sie tun können - Wenn Sie das neueste Update noch nicht installiert haben, warten Sie, bis wir hier posten, dass der Fix verfügbar ist. Sobald der Fix aus ist, aktualisieren Sie die AlertMedia App aus dem App Store.

2. 23. Oktober 2026 um 20:55 UTCmonitoring

   Die neue Version wartet noch auf eine endgültige Überprüfung von Apple.

3. 23. Oktober 2026 um 23:21 UTCmonitoring

   Die aktualisierte Version unserer iOS App wurde genehmigt. Wir warten darauf, dass es im Laden verteilt wird.

4. 23. Oktober 2026 um 23:40 UTCresolved

   Die neue Version der mobilen App steht im Apple App Store zum Download bereit.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. September 2026 um 16:40 UTCidentified

   Wir haben ein Problem mit einem unserer Messaging-Anbieter (Twilio) identifiziert, das sich auf die Zustellung einiger SMS-Nachrichten und Voice Delivery von der Plattform auswirkt (Benachrichtigungen, Bedrohungswarnungen, Reaktion auf Vorfälle, Reiserisikowarnungen). Unser Engineering-Team untersucht und überprüft Auswirkungen und mögliche Minderungsmaßnahmen. Wir arbeiten mit Twilio zusammen, um das Problem zu überwachen. Statusseite von Twilio: https://status.twilio.com/ Rund 10% der SMS-Nachrichten scheitern.

2. 1. September 2026 um 17:20 UTCidentified

   Wir beobachten weiterhin das Problem mit Twilio. Das Problem der Zustellbarkeit von Voice wurde identifiziert und ein Fix wird bereitgestellt. Das Problem für SMS-Verzögerungen wurde identifiziert und die Ingenieure arbeiten an einem Fix. Statusseite von Twilio: https://status.twilio.com/

3. 1. September 2026 um 17:36 UTCmonitoring

   Es wurden Korrekturen für SMS und Voice angewendet, und wir beginnen, eine Verringerung der Fehlerquoten zu sehen. Funktionalität für Voice und SMS wieder normal. Wir werden das Thema weiter verfolgen. Statusseite von Twilio: https://status.twilio.com/

4. 1. September 2026 um 18:26 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. Juni 2026 um 21: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. 4. Juni 2026 um 23:11 UTCinvestigating

   We are continuing to investigate the issue

3. 5. Juni 2026 um 00:07 UTCidentified

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

4. 5. Juni 2026 um 02:18 UTCmonitoring

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

5. 5. Juni 2026 um 14:19 UTCresolved

   This incident has been resolved.

1. 3. Juni 2026 um 19: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. 3. Juni 2026 um 21:03 UTCmonitoring

   We are currently deploying a fix for this issue.

3. 4. Juni 2026 um 02:09 UTCresolved

   This incident has been resolved.

1. 14. Januar 2026 um 18: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. 15. Januar 2026 um 03:32 UTCresolved

   The outage is resolved, according to Verizon.

1. 13. Januar 2026 um 19:17 UTCinvestigating

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

2. 13. Januar 2026 um 19:46 UTCidentified

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

3. 13. Januar 2026 um 19:58 UTCmonitoring

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

4. 13. Januar 2026 um 20:31 UTCresolved

   This incident has been resolved

1. 2. Dezember 2025 um 17:17 UTCinvestigating

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

2. 2. Dezember 2025 um 17:27 UTCmonitoring

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

3. 2. Dezember 2025 um 17:46 UTCresolved

   This incident has been resolved.

1. 18. November 2025 um 18: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. 18. November 2025 um 22:42 UTCresolved

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

1. 14. November 2025 um 20:04 UTCinvestigating

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

2. 15. November 2025 um 00:59 UTCmonitoring

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

3. 15. November 2025 um 02:27 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 09: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. 20. Oktober 2025 um 10:05 UTCidentified

   Notification sends are processing. Recovery in progress.

3. 20. Oktober 2025 um 10:05 UTCidentified

   Updated impacted components

4. 20. Oktober 2025 um 11:50 UTCidentified

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

5. 20. Oktober 2025 um 12:34 UTCidentified

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

6. 20. Oktober 2025 um 12:55 UTCidentified

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

7. 20. Oktober 2025 um 15:24 UTCidentified

   FTP Imports are not processing in either environment

8. 20. Oktober 2025 um 17:56 UTCidentified

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

9. 20. Oktober 2025 um 18:51 UTCidentified

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

10. 20. Oktober 2025 um 20:08 UTCmonitoring

    We are continuing to see delays in sending Threat Warnings

11. 20. Oktober 2025 um 21:00 UTCmonitoring

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

12. 20. Oktober 2025 um 21:04 UTCmonitoring

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

13. 21. Oktober 2025 um 09:09 UTCresolved

    This incident has been resolved.

1. 26. September 2025 um 15: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. 26. September 2025 um 15:22 UTCidentified

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

3. 26. September 2025 um 17:16 UTCmonitoring

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

4. 26. September 2025 um 17:31 UTCresolved

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

1. 13. Mai 2025 um 21: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. 13. Mai 2025 um 22: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. 13. Mai 2025 um 22: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. 14. Mai 2025 um 15:08 UTCmonitoring

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

3. 14. Mai 2025 um 19:56 UTCresolved

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

1. 26. März 2025 um 22: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. 26. März 2025 um 22:17 UTCresolved

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

1. 11. März 2025 um 17:49 UTCinvestigating

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

2. 11. März 2025 um 18:19 UTCmonitoring

   We are monitoring the issue, services are restored.

3. 11. März 2025 um 18:58 UTCresolved

   This incident has been resolved.

1. 20. Februar 2025 um 19:31 UTCinvestigating

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

2. 20. Februar 2025 um 19:37 UTCmonitoring

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

3. 20. Februar 2025 um 19:56 UTCresolved

   This incident has been resolved.

1. 13. Februar 2025 um 16:03 UTCinvestigating

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

2. 13. Februar 2025 um 16:19 UTCmonitoring

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

3. 13. Februar 2025 um 18:36 UTCresolved

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

1. 28. Januar 2025 um 13:50 UTCinvestigating

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

2. 28. Januar 2025 um 14: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. 28. Januar 2025 um 14:58 UTCresolved

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

1. 13. November 2024 um 13: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. 13. November 2024 um 14:37 UTCresolved

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

1. 26. September 2024 um 17:27 UTCinvestigating

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

2. 26. September 2024 um 17: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. 26. September 2024 um 17:53 UTCresolved

   This incident has been resolved.