Skip to main content
OneSignal

Journey / Event Streams/Outbound Data Integrations - delayed processing

Degraded Lasted 3h 8m · started · OneSignal's page

Level
confirmed
Worst impact
Degraded
Down Index
20of 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 3h 8m it lasted.

    Anything that failed between 2026-07-20 14:51 UTC and 2026-07-20 18: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 4

  1. investigating

    **What’s happening:** Journeys and webhook integrations are experiencing delayed processing. **Who’s affected:** All customers using Journeys or Webhook integrations are impacted. **Current Status:** We are investigating the issue and will provide an update in 20 minutes.

    provider

  2. investigating

    We are still investigating the issue. We will provide another update in 20 minutes

    provider

  3. investigating

    We are still investigating the issue. Journeys and Event Streams/ Outbound Data Integrations are delayed. We will provide another update in 20 minutes.

    provider

  4. resolved

    The issue has been resolved. All impacted systems are operating normally since 11:00 AM PT Monday.

    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-581f917dcc

Is OneSignal still down?

No, this incident was resolved 2026-07-20 18:00 UTC. For OneSignal's live state, see https://down.guide/onesignal.

How long did it last?

3h 8m, from 2026-07-20 14:51 UTC to 2026-07-20 18: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.