OneSignal incident: Journeys - delayed processing

1. resolvedJul 17, 2026, 23:06 UTC

   The issue has been resolved. All impacted systems are now operating normally. Event streams, data export integration, and journeys are all functioning normally now.

2. monitoringJul 17, 2026, 22:12 UTC

   We are currently adding more resources, but we aware we are experiencing journeys, event streams and data export integration delays.

3. monitoringJul 17, 2026, 20:52 UTC

   We are currently adding more resources, but we aware we are experiencing event streams and data export integration delays.

4. monitoringJul 17, 2026, 17:03 UTC

   We are monitoring the system as data gets replicated across additional resources.

5. resolvedJul 17, 2026, 04:00 UTC

   The issue has been resolved. All impacted systems are now operating normally.

6. monitoringJul 16, 2026, 23:15 UTC

   We continue to monitor the system as data gets replicated across additional resources.

7. monitoringJul 16, 2026, 19:46 UTC

   We continue to experience performance delays as more resources are added to our systems.

8. monitoringJul 16, 2026, 18:27 UTC

   In addition to Journeys and Message Event segment delays, Webhook delivery delays are currently ~1.2h. We will provide another update in 20.

9. monitoringJul 16, 2026, 17:10 UTC

   We have applied fixes. • Journeys is 30-45 minutes delayed • Message event segments could take ~45 minutes to come online

10. identifiedJul 16, 2026, 16:11 UTC

    We have identified the root cause and are working towards a resolution. We will provide another update in 20 minutes

11. investigatingJul 16, 2026, 15:45 UTC

    **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

12. investigatingJul 16, 2026, 15:32 UTC

    **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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in OneSignal's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mux: video live and playback issuesCritical · Jul 15, 2026, 19:13 UTC
• Render: GitHub outage affecting new service creation and service deploysCritical · Jul 16, 2026, 22:42 UTC
• Linear: Some customers are seeing issues with Linear loadingMajor · Jul 16, 2026, 16:47 UTC
• Inngest: Metrics Data DelaysMajor · Jul 16, 2026, 17:52 UTC
• Discord: API ErrorsMajor · Jul 17, 2026, 00:49 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• DigitalOcean: Reserved IP routing in TOR1Minor · Jul 16, 2026, 13:39 UTC
• RevenueCat: App Store Connect degraded performanceMinor · Jul 16, 2026, 13:47 UTC
• Tailscale: Coordination server issuesMinor · Jul 16, 2026, 14:38 UTC

How often does OneSignal have incidents?

OneSignal reported 9 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h 29m. See OneSignal's uptime and incident history