- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 12h 27m it lasted.
Anything that failed between 2026-07-16 15:32 UTC and 2026-07-17 04:00 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 12
- investigating
**What’s happening:** Journeys processing is delayed **Who’s affected:** • All customers using the Journeys feature **Current Status:** We are investigating the issue and will provide an update in 15 minutes.
provider
- investigating
**What’s happening:** Journeys processing is delayed **Who’s affected:** • All customers using the Journeys feature **Current Status:** We are investigating the issue and will provide an update in 15 minutes
provider
- identified
We have identified the root cause and are working towards a resolution. We will provide another update in 20 minutes
provider
- monitoring
We have applied fixes. • Journeys is 30-45 minutes delayed • Message event segments could take ~45 minutes to come online
provider
- monitoring
In addition to Journeys and Message Event segment delays, Webhook delivery delays are currently ~1.2h. We will provide another update in 20.
provider
- monitoring
We continue to experience performance delays as more resources are added to our systems.
provider
- monitoring
We continue to monitor the system as data gets replicated across additional resources.
provider
- resolved
The issue has been resolved. All impacted systems are now operating normally.
provider
- monitoring
We are monitoring the system as data gets replicated across additional resources.
provider
- monitoring
We are currently adding more resources, but we aware we are experiencing event streams and data export integration delays.
provider
- monitoring
We are currently adding more resources, but we aware we are experiencing journeys, event streams and data export integration delays.
provider
- resolved
The issue has been resolved. All impacted systems are now operating normally. Event streams, data export integration, and journeys are all functioning normally now.
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-8f7cee03ac
Is OneSignal still down?
No, this incident was resolved 2026-07-17 04:00 UTC. For OneSignal's live state, see https://down.guide/onesignal.
How long did it last?
12h 27m, from 2026-07-16 15:32 UTC to 2026-07-17 04:00 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.