Onesignal outage history

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

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 data. It came from a read-only database used for a limited share of read traffic, which we removed from service at 14:51 UTC on Oct 15. Results have been consistent since then. We are adding automated checks to prevent this from happening again. If you saw unexpected results during this window and need help, please contact support.

We're investigating the incident

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

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.

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

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

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

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 service. We will provide another update in 15 minutes.

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

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

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

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.

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

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

**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 and will provide an update in 30 minutes

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

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

We have applied a mitigation that resolves the impact.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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.

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

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

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.

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

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.

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

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

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

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.

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

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

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

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

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

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

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