OneSignal incident
Intermittent incomplete data in the dashboard and API reads for a subset of apps (starting with app id with 0)
OneSignal experienced a minor incident on October 14, 2026 affecting Push and Email and 1 more component, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 14, 2026, 02:31 PM UTC
Status: Identified We've identified an issue for a subset of apps (app IDs starting with 0). Affected components Integrations (Degraded performance) APIs & SDK Endpoints (Degraded performance) SMS (Degraded performance) In-App Messages (Degraded performance) Push (Degraded performance) Analytics & Reporting (Degraded performance) Dashboard / UI (Degraded performance) Email (Degraded performance)
- resolved Oct 15, 2026, 02:51 PM UTC
Status: Resolved 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. Affected components Analytics & Reporting (Operational) Dashboard / UI (Operational) Email (Operational) Integrations (Operational) APIs & SDK Endpoints (Operational) SMS (Operational) In-App Messages (Operational) Push (Operational)