Störungsverlauf von Onesignal

1. 4. August 2026 um 17:20 UTCinvestigating

   **What’s happening:** Apple push notifications are failing in about 3% of cases. "Unknown delivery error" or "APNS failed to provide a response" error responses may be seen. **Who’s affected:** • Customers using Apple Push Notifications **Current Status:** We are investigating the issue and will provide an update in 20

2. 4. August 2026 um 18:45 UTCidentified

   We have identified the root cause and are working towards a resolution. There was a slight change in how Apple's push notification connections work. We will provide another update in 20 minutes.

3. 4. August 2026 um 18:46 UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 20 minutes.

4. 4. August 2026 um 19:24 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. 30. Juli 2026 um 16:52 UTCinvestigating

   **Was passiert:** Das Laden von Nachrichtenereignissen auf die Benutzer- und Abonnementprofile wird zeitlich begrenzt. ** Wer ist betroffen:** Einige Kunden können langsame Ladezeiten oder Timeouts beim Laden von Nachrichtenereignissen im Benutzerprofil erleben ** Aktueller Status:** Wir untersuchen das Problem und werden in 30 Minuten ein Update bereitstellen

2. 30. Juli 2026 um 17:32 UTCresolved

   Das Problem ist gelöst. Alle betroffenen Systeme arbeiten jetzt normal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Juli 2026 um 17:56 UTCidentified

   Wir haben die Ursache identifiziert und arbeiten an einer Lösung.

2. 20. Juli 2026 um 17:56 UTCmonitoring

   Wir haben eine Abschwächung angewendet, die die Auswirkungen löst.

3. 20. Juli 2026 um 17:57 UTCresolved

   Das Problem ist gelöst. Alle betroffenen Systeme arbeiten jetzt normal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Juli 2026 um 16:16 UTCidentified

   Wir haben die Ursache identifiziert und fügen zusätzliche Ressourcen hinzu, um die Last besser zu bewältigen. Aktuell betroffene Komponenten sind Journeys, Event Streams und Outbound Data Integrations.

2. 21. Juli 2026 um 17:24 UTCresolved

   Das Problem ist gelöst. Alle betroffenen Systeme funktionieren ab Montag 11:00 Uhr PDT normal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Juli 2026 um 14:51 UTCinvestigating

   **Was passiert:** Journeys und Webhook-Integrationen erfahren eine verzögerte Verarbeitung. ** Wer ist betroffen:** Alle Kunden, die Journeys oder Webhook-Integrationen verwenden, sind betroffen. ** Aktueller Status:** Wir untersuchen das Problem und werden in 20 Minuten ein Update bereitstellen.

2. 20. Juli 2026 um 15:16 UTCinvestigating

   Wir untersuchen das Problem noch immer. Wir werden ein weiteres Update in 20 Minuten bereitstellen

3. 20. Juli 2026 um 15:27 UTCinvestigating

   Wir untersuchen das Problem noch immer. Journeys und Event Streams/Outbound Data Integrations verzögern sich. Wir werden in 20 Minuten ein weiteres Update bereitstellen.

4. 21. Juli 2026 um 15:39 UTCresolved

   Das Problem ist gelöst. Alle betroffenen Systeme funktionieren normal seit 11:00 Uhr PT Montag.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 15:32 UTCinvestigating

   **Was passiert:** Fahrtenverarbeitung verzögert sich ** Wer ist betroffen:** • Alle Kunden, die die Journeys-Funktion nutzen ** Aktueller Status:** Wir untersuchen das Problem und werden in 15 Minuten ein Update bereitstellen.

2. 16. Juli 2026 um 15:45 UTCinvestigating

   **Was passiert:** Fahrtenverarbeitung verzögert sich ** Wer ist betroffen:** • Alle Kunden, die die Journeys-Funktion nutzen ** Aktueller Status:** Wir untersuchen das Problem und werden in 15 Minuten ein Update bereitstellen

3. 16. Juli 2026 um 16:11 UTCidentified

   Wir haben die Ursache identifiziert und arbeiten an einer Lösung. Wir werden ein weiteres Update in 20 Minuten bereitstellen

4. 16. Juli 2026 um 17:10 UTCmonitoring

   Wir haben Fixes angewendet. • Fahrten sind 30-45 Minuten verspätet • Nachrichtenereignissegmente können etwa 45 Minuten dauern, bis sie online sind

5. 16. Juli 2026 um 18:27 UTCmonitoring

   Zusätzlich zu den Verzögerungen im Segment Journeys und Message Event betragen Webhook-Lieferverzögerungen derzeit ~1,2 Stunden. Wir werden ein weiteres Update in 20 geben.

6. 16. Juli 2026 um 19:46 UTCmonitoring

   Wir erleben weiterhin Leistungsverzögerungen, da unseren Systemen mehr Ressourcen hinzugefügt werden.

7. 16. Juli 2026 um 23:15 UTCmonitoring

   Wir überwachen das System weiterhin, da Daten über zusätzliche Ressourcen repliziert werden.

8. 17. Juli 2026 um 09:07 UTCresolved

   Das Problem ist gelöst. Alle betroffenen Systeme arbeiten jetzt normal.

9. 17. Juli 2026 um 17:03 UTCmonitoring

   Wir überwachen das System, da Daten über zusätzliche Ressourcen repliziert werden.

10. 17. Juli 2026 um 20:52 UTCmonitoring

    Wir fügen derzeit weitere Ressourcen hinzu, aber wir wissen, dass wir Ereignisströme und Verzögerungen bei der Integration von Datenexporten erleben.

11. 17. Juli 2026 um 22:12 UTCmonitoring

    Wir fügen derzeit weitere Ressourcen hinzu, aber wir wissen, dass wir Reisen, Ereignisströme und Verzögerungen bei der Integration von Datenexporten erleben.

12. 17. Juli 2026 um 23:06 UTCresolved

    Das Problem ist gelöst. Alle betroffenen Systeme arbeiten jetzt normal. Event-Streams, Datenexport-Integration und Journeys funktionieren jetzt alle normal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. Juli 2026 um 17:05 UTCinvestigating

   **What’s happening:** Some customers are experiencing delayed delivery of event streams and webhooks **Who’s affected:** All customers using event streams and webhooks **Current Status:** We are investigating the issue and will provide an update in 15 minutes

2. 6. Juli 2026 um 17:11 UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 15 minutes.

3. 6. Juli 2026 um 18:20 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. 1. Juli 2026 um 22:11 UTCidentified

   We have identified the root cause and are working towards a resolution. Customers may experience users not progressing through their Journeys We will provide another update in 30 minutes.

2. 1. Juli 2026 um 22:39 UTCmonitoring

   We have performed the necessary mitigation and customer journeys are now progressing successfully. Some customers may experience a 5-10 minutes lag

3. 1. Juli 2026 um 22:50 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. 25. Juni 2026 um 08:11 UTCinvestigating

   **What’s happening:** Analytics and reporting could be delayed. **Who’s affected:** All customers _may_ be affected **Current Status:** We are investigating the issue and will provide an update in 15m

2. 25. Juni 2026 um 08:34 UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. Analytics are delayed, but we’re processing the lag. We will provide another update in 15 minutes.

3. 25. Juni 2026 um 08:49 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. The analytic lag is totally processed.

1. 22. Juni 2026 um 07:20 UTCresolved

   Due to an infrastructure issue, some customers were temporarily unable to view message events on the user and subscription profile pages. The issue has since been resolved.

1. 17. Juni 2026 um 06:24 UTCinvestigating

   **What’s happening:** Delivery of inteligent/timezone notifications will be delayed, we’re investigating the situation **Who’s affected:** • All customers _may_ be affected **Current Status:** We are investigating the issue and will provide an update in 10 minutes

2. 17. Juni 2026 um 06:38 UTCidentified

   We have identified the root cause and are working towards a resolution. We will provide another update in 15 minutes

3. 17. Juni 2026 um 06:55 UTCresolved

   We have applied a mitigation that resolves the impact. We are monitoring to confirm effectiveness. Intelligent/timezone notifications were delayed for 45m. **No** regular direct notifications were impacted.

1. 9. Juni 2026 um 19:01 UTCinvestigating

   **What’s happening:** Users may be experiencing issues interacting with the dashboard **Who’s affected:** • Customers interacting with the dashboard **Current Status:** We are investigating the issue and will provide an update in [2 minutes]

2. 9. Juni 2026 um 19:13 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. The root cause of the issue was a faulty configuration change to our authentication system. The change has been reverted and all systems now operational.

1. 1. Juni 2026 um 23:28 UTCinvestigating

   **What’s happening:** We are currently investigating an issue affecting Dashboard login. Users attempting to authenticate may experience login failures or be unable to access their accounts. Our team is actively working to identify the root cause and restore normal functionality. **Who’s affected:** Users who need to sign into the dashboard-It may be unable to log in. **Current Status:** We are investigating the issue and will provide an update in 30 minutes

2. 1. Juni 2026 um 23:46 UTCidentified

   We have identified the root cause and are working towards a resolution. We will provide another update in 20 minutes.

3. 2. Juni 2026 um 00:12 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. Dashboard logins are now resolved.

1. 22. Mai 2026 um 20:50 UTCmonitoring

   Event Streams, Journey Webhooks, and Data Warehouse exports are delayed. We have identified the cause and resolved the issue. Systems are working through the backlog of events.

2. 22. Mai 2026 um 22:16 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. 22. Mai 2026 um 19:37 UTCinvestigating

   **What’s happening:** Timezone based and intelligent deliveries impacted because of backlog of messages. **Who’s affected:** • Any free customers using Timezone-based Delivery, Intelligent Delivery, or Retry Delivery. **Current Status:** We are investigating the issue and will provide an update in 30 minutes

2. 22. Mai 2026 um 19:46 UTCidentified

   We've identified the root cause and are actively implementing mitigations.

3. 22. Mai 2026 um 20:23 UTCresolved

   The necessary mitigations have been applied and all systems are now operating normally.

1. 11. Mai 2026 um 18:19 UTCinvestigating

   **What’s happening:** Some customers are unable to access the dashboard or API **Who’s affected:** • Customers with an app id starting with 2 **Current Status:** We are investigating the issue and will provide an update in 15 minutes

2. 11. Mai 2026 um 18:36 UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 30 minutes.

3. 11. Mai 2026 um 18:44 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. 24. April 2026 um 18:25 UTCinvestigating

   **What’s happening:** Dashboard and API users currently experiencing sporadic instability **Who’s affected:** • All customers using the dashboard, creating messages in the dashboard **Current Status:** We are investigating the issue and will provide an update in a few minutes Update: we are scaling hardware resources to resolve this issue.

2. 24. April 2026 um 19:16 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. Hardware resources have been scaled up.

1. 13. April 2026 um 22:00 UTCmonitoring

   We have applied a mitigation that should resolve the impact of degraded dashboard user experience and potential delivery failure for dashboard users. We are monitoring to confirm effectiveness. We will provide another update in 5.

2. 13. April 2026 um 22:07 UTCresolved

   Incident is resolved.

1. 9. April 2026 um 18:58 UTCmonitoring

   During a brief period, some customers may have experienced errors while loading their app metrics. We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. During this period, some customers may have experienced errors loading app metrics on the OneSignal dashboard for analytics. We will provide another update in 30 minutes.

2. 9. April 2026 um 19:37 UTCmonitoring

   Our engineering team continues to monitor our systems. We are no longer seeing any impact and all systems are operational.

3. 9. April 2026 um 19:54 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. 9. April 2026 um 14:46 UTCinvestigating

   **What’s happening:** Customers attempting to use the dashboard and API are encountering errors. **Who’s affected:** All customers attempting to use the dashboard and API **Current Status:** We are investigating the issue and will provide an update in 10 minutes

2. 9. April 2026 um 14:55 UTCidentified

   We have identified the root cause and are working towards a resolution. We will provide another update in 10 minutes.

3. 9. April 2026 um 14:59 UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 10 minutes.

4. 9. April 2026 um 15:06 UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.