OneSignal Outage History
29 incidents recorded over the last 365 days, 29 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded OneSignal Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 20, 2026 | Intermittent incomplete data in the dashboard and API reads for a subset of apps (starting with app id 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… | -7562 min | Resolved |
| Sep 30, 2026 | Database incident - impacting app IDs starting with eWe 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. | -10 min | Resolved |
| Sep 22, 2026 | Subscription API - Creation FailuresThe issue has been resolved. All impacted systems are now operating normally. | 2 min | Resolved |
| Sep 18, 2026 | Intermittent errors on /api/v1/notifications api/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. | 34 min | Resolved |
| Aug 4, 2026 | Apple push notifications failing in about 3% of casesThe issue has been resolved. All impacted systems are now operating normally. | 2h 4m | Resolved |
| Jul 30, 2026 | Message events on user and subscription profiles slow and timing outThe issue has been resolved. All impacted systems are now operating normally. | 40 min | Resolved |
| Jul 20, 2026 | Issue has been identifiedThe issue has been resolved. All impacted systems are now operating normally. | 0 min | Resolved |
| Jul 20, 2026 | Issue identified and additional resources being addedThe issue has been resolved. All impacted systems are now operating normally as of Monday 11:00 AM PDT. | 1h 43m | Resolved |
| Jul 20, 2026 | Journey / Event Streams/Outbound Data Integrations - delayed processingThe issue has been resolved. All impacted systems are operating normally since 11:00 AM PT Monday. | 3h 8m | Resolved |
| Jul 16, 2026 | Journeys - delayed processingThe issue has been resolved. All impacted systems are now operating normally. Event streams, data export integration, and journeys are all functioning normally now. | 12h 27m | Resolved |
| Jul 6, 2026 | Event streams - Delayed DeliveryThe issue has been resolved. All impacted systems are now operating normally. | 1h 14m | Resolved |
| Jul 1, 2026 | Users not progressing through journeysThe issue has been resolved. All impacted systems are now operating normally. | 39 min | Resolved |
| Jun 25, 2026 | Analytics & Reporting - processing is delayedThe issue has been resolved. All impacted systems are now operating normally. The analytic lag is totally processed. | 38 min | Resolved |
| Jun 22, 2026 | Customers unable to view message events in user and subscription profilesDue 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. | -440 min | Resolved |
| Jun 17, 2026 | Message Delivery - Delayed inteligent/timezone notification deliveriesWe 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. | 30 min | Resolved |
| Jun 9, 2026 | Dashboard - intermittent issues interacting with dashboardThe 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… | 11 min | Resolved |
| Jun 1, 2026 | Users Unable to Sign In with GoogleThe issue has been resolved. All impacted systems are now operating normally. Dashboard logins are now resolved. | 44 min | Resolved |
| May 22, 2026 | Event Export DelayThe issue has been resolved. All impacted systems are now operating normally. | 1h 25m | Resolved |
| May 22, 2026 | Delay in deliveries impacting free customersThe necessary mitigations have been applied and all systems are now operating normally. | 46 min | Resolved |
| May 11, 2026 | Dashboard & API - Partial OutageThe issue has been resolved. All impacted systems are now operating normally. | 25 min | Resolved |
| Apr 24, 2026 | [Dashboard & API] - [elevated error rates]The issue has been resolved. All impacted systems are now operating normally. Hardware resources have been scaled up. | 51 min | Resolved |
| Apr 13, 2026 | [Database connectivity] - [Dashboard users]Incident is resolved. | 7 min | Resolved |
| Apr 9, 2026 | Elevated errors while displaying app metricsThe issue has been resolved. All impacted systems are now operating normally. | 56 min | Resolved |
| Apr 9, 2026 | Dashboard and API outageThe issue has been resolved. All impacted systems are now operating normally. | 17 min | Resolved |
| Apr 9, 2026 | Dashboard - API latency increasesThe issue has been resolved. All impacted systems are now operating normally. | 45 min | Resolved |
| Apr 8, 2026 | Incorrect segment membership impacted some usersOur engineering team identified the issue internally and has completed the necessary mitigation and resolution steps. | -10414 min | Resolved |
| Mar 20, 2026 | Intermittent errors from Notification Create endpointThe issue has been resolved. All impacted systems are now operating normally. Over the course of the incident a few thousand HTTP 500s occurred. | 48 min | Resolved |
| Mar 20, 2026 | Email deliveries are experiencing delays and potential failuresThe team has been monitoring the delivery pods and is no longer seeing any errors or stuck deliveries. All previously stuck notifications have been successfully retried. | 3h 3m | Resolved |
| Mar 19, 2026 | web requests - user access and service reliability affected for ~5% of users for ~2 minThe issue has been resolved. All impacted systems are now operating normally. | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next OneSignal incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This OneSignal Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before OneSignal acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single OneSignal outage in this window ran 12h 27m, against a mean recovery of 1h 22m. If you depend on OneSignal in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.