- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 10of 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 1m it lasted.
Anything that failed between 2026-07-20 17:56 UTC and 2026-07-20 17:57 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
- identified
We have identified the root cause and are working towards a resolution.
provider
- monitoring
We have applied a mitigation that resolves the impact.
provider
- resolved
The issue has been resolved. All impacted 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-7613030110
Is OneSignal still down?
No, this incident was resolved 2026-07-20 17:57 UTC. For OneSignal's live state, see https://down.guide/onesignal.
How long did it last?
1m, from 2026-07-20 17:56 UTC to 2026-07-20 17:57 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.