- 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 56m it lasted.
Anything that failed between 2026-04-09 18:58 UTC and 2026-04-09 19:54 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
- monitoring
During a brief period, some customers may have experienced errors while loading their app metrics. We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. During this period, some customers may have experienced errors loading app metrics on the OneSignal dashboard for analytics. We will provide another update in 30 minutes.
provider
- monitoring
Our engineering team continues to monitor our systems. We are no longer seeing any impact and all systems are operational.
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-e74ffbff04
Is OneSignal still down?
No, this incident was resolved 2026-04-09 19:54 UTC. For OneSignal's live state, see https://down.guide/onesignal.
How long did it last?
56m, from 2026-04-09 18:58 UTC to 2026-04-09 19:54 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.