# Journey / Event Streams/Outbound Data Integrations - delayed processing

- Provider: [OneSignal](https://down.guide/providers/onesignal)
- Confidence: Confirmed
- Impact: Degraded
- lasted 3h 8m
- started 2026-07-20 14:51 UTC
- id: DWN-581f917dcc
- Official page: https://status.onesignal.com/incidents/01KY006B3R8AEF10VSW0RNAK50

## Updates from OneSignal
### 2026-07-20 14:51 UTC: 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.

### 2026-07-20 15:16 UTC: investigating
We are still investigating the issue.
We will provide another update in 20 minutes

### 2026-07-20 15:27 UTC: investigating
We are still investigating the issue. Journeys and Event Streams/ Outbound Data Integrations are delayed.
We will provide another update in 20 minutes.

### 2026-07-20 18:00 UTC: resolved
The issue has been resolved. All impacted systems are operating normally since 11:00 AM PT Monday.

From the builder: does your app depend on OneSignal? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=onesignal) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention OneSignal.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-581f917dcc), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.