Onesignal driftsforstyrrelser

1. 4. august 2026 kl. 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 kl. 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 kl. 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 kl. 19.24 UTCresolved

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

1. 30. juli 2026 kl. 16.52 UTCinvestigating

   Hvad sker der? Indlæser meddelelser begivenheder på brugeren og abonnement profiler er timing ud. * * Hvem er påvirket: * * • Nogle kunder kan opleve langsomme belastningstider eller timeouts ved indlæsning af meddelelser på brugerprofilen * * Nuværende status: * * Vi er ved at undersøge problemet og vil levere en opdatering på 30 minutter

2. 30. juli 2026 kl. 17.32 UTCresolved

   Spørgsmålet er løst. Alle angrebne systemer fungerer nu normalt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. juli 2026 kl. 17.56 UTCidentified

   Vi har identificeret årsagen og arbejder hen imod en beslutning.

2. 20. juli 2026 kl. 17.56 UTCmonitoring

   Vi har anvendt en afbødning, der løser virkningen.

3. 20. juli 2026 kl. 17.57 UTCresolved

   Spørgsmålet er løst. Alle angrebne systemer fungerer nu normalt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. juli 2026 kl. 16.16 UTCidentified

   Vi har identificeret årsagen og tilføjer yderligere ressourcer til bedre håndtering af belastningen. I øjeblikket berørte komponenter er Rejse, Event Streams, og Outbound Data Integrationer.

2. 21. juli 2026 kl. 17.24 UTCresolved

   Spørgsmålet er løst. Alle angrebne systemer fungerer nu normalt fra mandag 11: 00 PDT.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. juli 2026 kl. 14.51 UTCinvestigating

   Hvad sker der? Rejse og webhook-integration oplever forsinket behandling. * * Hvem er påvirket: * * Alle kunder, der bruger rejser eller Webhook integration er påvirket. * * Nuværende status: * * Vi undersøger sagen og vil opdatere den om 20 minutter.

2. 20. juli 2026 kl. 15.16 UTCinvestigating

   Vi undersøger stadig spørgsmålet. Vi vil levere endnu en opdatering om 20 minutter

3. 20. juli 2026 kl. 15.27 UTCinvestigating

   Vi undersøger stadig spørgsmålet. Rejse og event Streams / Outbound Data Integrationer er forsinket. Vi vil levere endnu en opdatering om 20 minutter.

4. 21. juli 2026 kl. 15.39 UTCresolved

   Spørgsmålet er løst. Alle systemer fungerer normalt siden kl. 11: 00 PT mandag.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. juli 2026 kl. 15.32 UTCinvestigating

   Hvad sker der? Rejsebehandling er forsinket * * Hvem er påvirket: * * • Alle kunder, der bruger funktionen Rejse * * Nuværende status: * * Vi er ved at undersøge spørgsmålet og vil levere en opdatering om 15 minutter.

2. 16. juli 2026 kl. 15.45 UTCinvestigating

   Hvad sker der? Rejsebehandling er forsinket * * Hvem er påvirket: * * • Alle kunder, der bruger funktionen Rejse * * Nuværende status: * * Vi er ved at undersøge problemet og vil levere en opdatering om 15 minutter

3. 16. juli 2026 kl. 16.11 UTCidentified

   Vi har identificeret årsagen og arbejder hen imod en beslutning. Vi vil levere endnu en opdatering om 20 minutter

4. 16. juli 2026 kl. 17.10 UTCmonitoring

   Vi har anvendt rettelser. • Rejse er 30-45 minutter forsinket • Brev begivenhed segmenter kunne tage ~ 45 minutter at komme online

5. 16. juli 2026 kl. 18.27 UTCmonitoring

   Ud over rejser og Besked Event segment forsinkelser, Webhook levering forsinkelser er i øjeblikket ~ 1.2h. Vi giver endnu en opdatering om 20.

6. 16. juli 2026 kl. 19.46 UTCmonitoring

   Vi oplever fortsat forsinkelser i udførelsen, efterhånden som der tilføres flere ressourcer til vores systemer.

7. 16. juli 2026 kl. 23.15 UTCmonitoring

   Vi fortsætter med at overvåge systemet som data bliver kopieret på tværs af yderligere ressourcer.

8. 17. juli 2026 kl. 09.07 UTCresolved

   Spørgsmålet er løst. Alle angrebne systemer fungerer nu normalt.

9. 17. juli 2026 kl. 17.03 UTCmonitoring

   Vi overvåger systemet som data bliver kopieret på tværs af yderligere ressourcer.

10. 17. juli 2026 kl. 20.52 UTCmonitoring

    Vi tilføjer i øjeblikket flere ressourcer, men vi er klar over, at vi oplever forsinkelser i forbindelse med eksport af data.

11. 17. juli 2026 kl. 22.12 UTCmonitoring

    Vi tilføjer i øjeblikket flere ressourcer, men vi er klar over, at vi oplever forsinkelser i forbindelse med rejser, begivenheder og dataeksport.

12. 17. juli 2026 kl. 23.06 UTCresolved

    Spørgsmålet er løst. Alle angrebne systemer fungerer nu normalt. Begivenhedsstrømme, dataeksport integration, og rejser er alle fungerer normalt nu.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 6. juli 2026 kl. 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 kl. 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 kl. 18.20 UTCresolved

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

1. 1. juli 2026 kl. 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 kl. 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 kl. 22.50 UTCresolved

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

1. 25. juni 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 00.12 UTCresolved

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

1. 22. maj 2026 kl. 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. maj 2026 kl. 22.16 UTCresolved

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

1. 22. maj 2026 kl. 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. maj 2026 kl. 19.46 UTCidentified

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

3. 22. maj 2026 kl. 20.23 UTCresolved

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

1. 11. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 18.44 UTCresolved

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

1. 24. april 2026 kl. 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 kl. 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 kl. 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 kl. 22.07 UTCresolved

   Incident is resolved.

1. 9. april 2026 kl. 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 kl. 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 kl. 19.54 UTCresolved

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

1. 9. april 2026 kl. 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 kl. 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 kl. 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 kl. 15.06 UTCresolved

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