Intermittent incomplete data in the dashboard and API reads for a subset of apps (starting with app id with 0)

What to do

• Check whether your product depends on OneSignal. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-20 20:53 UTC and 2026-10-15 14:51 UTC may need a replay.

• Subscribe to OneSignal's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=onesignal works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from OneSignal 2

1. identifiedOct 14, 2026, 2:31 PM UTC

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

   provider

2. resolvedOct 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 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.