- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
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 47m it lasted.
Anything that failed between 2026-05-22 19:37 UTC and 2026-05-22 20:23 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 3
- investigating
**What’s happening:** Timezone based and intelligent deliveries impacted because of backlog of messages. **Who’s affected:** • Any free customers using Timezone-based Delivery, Intelligent Delivery, or Retry Delivery. **Current Status:** We are investigating the issue and will provide an update in 30 minutes
provider
- identified
We've identified the root cause and are actively implementing mitigations.
provider
- resolved
The necessary mitigations have been applied and all systems are now operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f8a6e5a206
Is OneSignal still down?
No, this incident was resolved 2026-05-22 20:23 UTC. For OneSignal's live state, see https://down.guide/onesignal.
How long did it last?
47m, from 2026-05-22 19:37 UTC to 2026-05-22 20:23 UTC, by the times OneSignal posted.
What caused it?
OneSignal hasn't published a root cause. If it does, it shows here.
Where does this come from?
OneSignal's official status page, https://status.onesignal.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.