We started checking OneSignal on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when OneSignal reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what OneSignal's own status page declared. Below it, any public chatter we saw about OneSignal and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what OneSignal's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about OneSignal in the last 24 hours, which is not evidence that nothing is wrong.
OneSignal's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is OneSignal's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention OneSignal next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
579
US-West
99.78%
447
Europe
100.00%
405
Asia-Pacific
100.00%
245
Their declared record
OneSignal's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Intermittent incomplete data in the dashboard and API reads for a subset of apps (starting with app id with 0)Minor incident
Oct 14, 2026, 2:31 PM UTC to Oct 15, 2026, 2:51 PM UTC (1d 0h)resolved
their latest update (Oct 15, 2026, 2:51 PM 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 da…
Database incident - impacting app IDs starting with eMinor incident
Sep 30, 2026, 8:48 AM UTC to Sep 30, 2026, 9:12 AM UTC (24 min)resolved
their latest update (Sep 30, 2026, 9:12 AM 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.
Subscription API - Creation FailuresPartial outage
Sep 22, 2026, 9:28 PM UTC to Sep 22, 2026, 9:30 PM UTC (2 min)resolved
their latest update (Sep 22, 2026, 9:30 PM UTC): The issue has been resolved. All impacted systems are now operating normally.
Intermittent errors on /api/v1/notifications apiPartial outage
Sep 18, 2026, 12:48 AM UTC to Sep 18, 2026, 1:23 AM UTC (34 min)resolved
their latest update (Sep 18, 2026, 1:23 AM 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.
Apple push notifications failing in about 3% of casesPartial outage
Aug 4, 2026, 5:20 PM UTC to Aug 4, 2026, 7:24 PM UTC (2h 4m)resolved
their latest update (Aug 4, 2026, 7:24 PM UTC): The issue has been resolved. All impacted systems are now operating normally.
Message events on user and subscription profiles slow and timing outMinor incident
Jul 30, 2026, 4:52 PM UTC to Jul 30, 2026, 5:32 PM UTC (40 min)resolved
their latest update (Jul 30, 2026, 5:32 PM UTC): The issue has been resolved. All impacted systems are now operating normally.
Issue has been identifiedAll systems operational
Jul 20, 2026, 5:56 PM UTC to Jul 20, 2026, 5:57 PM UTC (1 min)resolved
their latest update (Jul 20, 2026, 5:57 PM UTC): The issue has been resolved. All impacted systems are now operating normally.
Issue identified and additional resources being addedMinor incident
Jul 20, 2026, 4:16 PM UTC to Jul 20, 2026, 6:00 PM UTC (1h 44m)resolved
their latest update (Jul 20, 2026, 6:00 PM UTC): The issue has been resolved. All impacted systems are now operating normally as of Monday 11:00 AM PDT.
Journey / Event Streams/Outbound Data Integrations - delayed processingMinor incident
Jul 20, 2026, 2:51 PM UTC to Jul 20, 2026, 6:00 PM UTC (3h 8m)resolved
their latest update (Jul 20, 2026, 6:00 PM UTC): The issue has been resolved. All impacted systems are operating normally since 11:00 AM PT Monday.
Journeys - delayed processingMinor incident
Jul 16, 2026, 3:32 PM UTC to Jul 17, 2026, 4:00 AM UTC (12h 27m)resolved
their latest update (Jul 17, 2026, 11:06 PM 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.
Showing the 10 most recent of 25 incidents OneSignal has declared in the history we hold.
These entries are OneSignal's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
OneSignal's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.