OneSignal incident

Journeys - delayed processing

Minor Resolved View vendor source →

OneSignal experienced a minor incident on July 16, 2026 affecting Journeys and Integrations, lasting 1d 7h. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2026, 03:32 PM UTC
Resolved
Jul 17, 2026, 11:06 PM UTC
Duration
1d 7h
Detected by Pingoru
Jul 16, 2026, 03:32 PM UTC

Affected components

JourneysIntegrations

Update timeline

  1. investigating Jul 16, 2026, 03:32 PM UTC

    Status: 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. Affected components Journeys (Degraded performance)

  2. investigating Jul 16, 2026, 03:45 PM UTC

    Status: 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 Affected components Journeys (Degraded performance)

  3. identified Jul 16, 2026, 04:11 PM UTC

    Status: Identified We have identified the root cause and are working towards a resolution. We will provide another update in 20 minutes Affected components Journeys (Degraded performance)

  4. monitoring Jul 16, 2026, 05:10 PM UTC

    Status: Monitoring We have applied fixes. • Journeys is 30-45 minutes delayed • Message event segments could take ~45 minutes to come online Affected components Journeys (Degraded performance)

  5. monitoring Jul 16, 2026, 06:27 PM UTC

    Status: Monitoring In addition to Journeys and Message Event segment delays, Webhook delivery delays are currently ~1.2h. We will provide another update in 20. Affected components Journeys (Degraded performance)

  6. monitoring Jul 16, 2026, 07:46 PM UTC

    Status: Monitoring We continue to experience performance delays as more resources are added to our systems. Affected components Journeys (Degraded performance)

  7. monitoring Jul 16, 2026, 11:15 PM UTC

    Status: Monitoring We continue to monitor the system as data gets replicated across additional resources. Affected components Journeys (Degraded performance)

  8. resolved Jul 17, 2026, 04:00 AM UTC

    Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Journeys (Operational)

  9. monitoring Jul 17, 2026, 05:03 PM UTC

    Status: Monitoring We are monitoring the system as data gets replicated across additional resources. Affected components Journeys (Degraded performance)

  10. monitoring Jul 17, 2026, 08:52 PM UTC

    Status: Monitoring We are currently adding more resources, but we aware we are experiencing event streams and data export integration delays. Affected components Journeys (Degraded performance)

  11. monitoring Jul 17, 2026, 10:12 PM UTC

    Status: Monitoring We are currently adding more resources, but we aware we are experiencing journeys, event streams and data export integration delays. Affected components Integrations (Degraded performance) Journeys (Degraded performance)

  12. resolved Jul 17, 2026, 11:06 PM UTC

    Status: 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. Affected components Integrations (Operational) Journeys (Operational)