Changes / OneSignal / Intermittent errors on /api/v1/notifications api
OneSignal: Major incident: Intermittent errors on /api/v1/notifications api
Summary
OneSignal reported major intermittent errors creating notifications through /api/v1/notifications, affecting some customers from 2026-09-18 00:48 UTC until resolution at 2026-09-18 01:23 UTC (34 min). Heavy load on a notification service caused the errors; OneSignal scaled up resources and confirmed the endpoint was stable for all customers.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 80%)Changed Detected Source: status.onesignal.com (opens in new tab)
What changed
Before: not present
After: Intermittent errors on /api/v1/notifications api
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-18 00:48 UTC
Before: not present
After: 2026-09-18 01:23 UTC
Before: not present
After: 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.
Before: not present
After: A fix is rolling out now for the affected notifications services that are overloaded. Things should be stable within the next 10 minutes.
Before: not present
After: /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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Intermittent errors on /api/v1/notifications api (this change) OneSignal reported major intermittent errors creating notifications through /api/v1/notifications, affecting some customers from 2026-09-18 00:48 UTC until resolution at 2026-09-18 01:23 UTC (34 min). Heavy load on a notification service caused the errors; OneSignal scaled up resources and confirmed the endpoint was stable for all customers. | Major incident |
All OneSignal changes → · OneSignal profile · Markdown · JSON