OneSignal

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-14 14:31 UTC

   We've identified an issue for a subset of apps (app IDs starting with 0).

2. resolved 2026-10-15 14:51 UTC

   Between 14:31 UTC on Oct 14 and 14:51 UTC on Oct 15, 2026, a subset of apps (apps whose app ID starts with 0) may have intermittently seen incomplete or inconsistent results. The issue affected read requests only. No data was lost, and our primary systems never had incomplete...

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-30 08:48 UTC

   We're investigating the incident

2. monitoring 2026-09-30 09:07 UTC

   We've identified the problem and applied a fix. Traffic is being restored.

3. resolved 2026-09-30 09:12 UTC

   We experienced a database issue that affected our customers. It only impacted apps which IDs start with e. The team has resolved the incident, and traffic is back to normal.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 21:05 UTC

   **What’s happening:** Customers are unable to create new subscriptions **Who’s affected:** All customers trying to create new subscriptions **Current Status:** We are investigating the issue

2. monitoring 2026-09-22 21:19 UTC

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness.

3. resolved 2026-09-22 21:30 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-18 00:48 UTC

   We have identified the root cause and are working towards a resolution. Heavy load on one of our notification services is causing intermittent errors when trying to create a notification. Not all customers are affected. The team is working on adding more capacity to the affected...

2. identified 2026-09-18 01:13 UTC

   A fix is rolling out now for the affected notifications services that are overloaded. Things should be stable within the next 10 minutes.

3. resolved 2026-09-18 01:23 UTC

   /api/v1/notifications create endpoint is now stable for all customers. The team has scaled up resources to handle increased load on our notifications service.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-04 17:20 UTC

   **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...

2. identified 2026-08-04 18:45 UTC

   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. monitoring 2026-08-04 18:46 UTC

   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. resolved 2026-08-04 19:24 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 16:52 UTC

   **What’s happening:** Loading message events on the user and subscription profiles is timing out. **Who’s affected:** • Some customers may experience slow load times or timeouts when loading message events on the user profile **Current Status:** We are investigating the issue...

2. resolved 2026-07-30 17:32 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-20 17:56 UTC

   We have identified the root cause and are working towards a resolution.

2. monitoring 2026-07-20 17:56 UTC

   We have applied a mitigation that resolves the impact.

3. resolved 2026-07-20 17:57 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-20 16:16 UTC

   We have identified the root cause and are adding additional resources to better handle the load. Currently affected components are Journeys, Event Streams, and Outbound Data Integrations.

2. resolved 2026-07-20 18:00 UTC

   The issue has been resolved. All impacted systems are now operating normally as of Monday 11:00 AM PDT.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-20 14:51 UTC

   **What’s happening:** Journeys and webhook integrations are experiencing delayed processing. **Who’s affected:** All customers using Journeys or Webhook integrations are impacted. **Current Status:** We are investigating the issue and will provide an update in 20 minutes.

2. investigating 2026-07-20 15:16 UTC

   We are still investigating the issue. We will provide another update in 20 minutes

3. investigating 2026-07-20 15:27 UTC

   We are still investigating the issue. Journeys and Event Streams/ Outbound Data Integrations are delayed. We will provide another update in 20 minutes.

4. resolved 2026-07-20 18:00 UTC

   The issue has been resolved. All impacted systems are operating normally since 11:00 AM PT Monday.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-16 15:32 UTC

   **What’s happening:** Journeys processing is delayed **Who’s affected:** • All customers using the Journeys feature **Current Status:** We are investigating the issue and will provide an update in 15 minutes.

2. investigating 2026-07-16 15:45 UTC

   **What’s happening:** Journeys processing is delayed **Who’s affected:** • All customers using the Journeys feature **Current Status:** We are investigating the issue and will provide an update in 15 minutes

3. identified 2026-07-16 16:11 UTC

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

4. monitoring 2026-07-16 17:10 UTC

   We have applied fixes. • Journeys is 30-45 minutes delayed • Message event segments could take ~45 minutes to come online

5. monitoring 2026-07-16 18:27 UTC

   In addition to Journeys and Message Event segment delays, Webhook delivery delays are currently ~1.2h. We will provide another update in 20.

6. monitoring 2026-07-16 19:46 UTC

   We continue to experience performance delays as more resources are added to our systems.

7. monitoring 2026-07-16 23:15 UTC

   We continue to monitor the system as data gets replicated across additional resources.

8. resolved 2026-07-17 04:00 UTC

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

9. monitoring 2026-07-17 17:03 UTC

   We are monitoring the system as data gets replicated across additional resources.

10. monitoring 2026-07-17 20:52 UTC

    We are currently adding more resources, but we aware we are experiencing event streams and data export integration delays.

11. monitoring 2026-07-17 22:12 UTC

    We are currently adding more resources, but we aware we are experiencing journeys, event streams and data export integration delays.

12. resolved 2026-07-17 23:06 UTC

    The issue has been resolved. All impacted systems are now operating normally. Event streams, data export integration, and journeys are all functioning normally now.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-06 17:05 UTC

   **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. monitoring 2026-07-06 17:11 UTC

   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. resolved 2026-07-06 18:20 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-01 22:11 UTC

   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. monitoring 2026-07-01 22:39 UTC

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

3. resolved 2026-07-01 22:50 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 08:11 UTC

   **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. monitoring 2026-06-25 08:34 UTC

   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. resolved 2026-06-25 08:49 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-06-22 00:00 UTC

   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.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-17 06:24 UTC

   **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. identified 2026-06-17 06:38 UTC

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

3. resolved 2026-06-17 06:55 UTC

   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.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-09 19:01 UTC

   **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. resolved 2026-06-09 19:13 UTC

   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.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-01 23:28 UTC

   **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...

2. identified 2026-06-01 23:46 UTC

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

3. resolved 2026-06-02 00:12 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-22 20:50 UTC

   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. resolved 2026-05-22 22:16 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 19:37 UTC

   **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...

2. identified 2026-05-22 19:46 UTC

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

3. resolved 2026-05-22 20:23 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-11 17:55 UTC

   **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. monitoring 2026-05-11 18:36 UTC

   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. resolved 2026-05-11 18:44 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-24 18:25 UTC

   **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...

2. resolved 2026-04-24 19:16 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-13 22:00 UTC

   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. resolved 2026-04-13 22:07 UTC

   Incident is resolved.

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-09 18:58 UTC

   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...

2. monitoring 2026-04-09 19:37 UTC

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

3. resolved 2026-04-09 19:54 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-09 14:37 UTC

   **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. identified 2026-04-09 14:50 UTC

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

3. monitoring 2026-04-09 14:54 UTC

   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. resolved 2026-04-09 15:04 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-09 14:10 UTC

   **What’s happening:** Dashboard and API request are increased **Who’s affected:** All customers _may_ be affected **Current Status:** We are investigating the issue and will provide an update in 10 minutes

2. monitoring 2026-04-09 14:33 UTC

   We have identified the root cause and rolled a resolution. We’re currently monitoring and expect dashboard and API to work as expected again, We will provide another update in 5 minutes

3. resolved 2026-04-09 15:06 UTC

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

Excerpts are shortened. Read the full incident on OneSignal's status page.