OneSignal incident: Issue identified and additional resources being added

1. resolvedJul 20, 2026, 18:00 UTC

   The issue has been resolved. All impacted systems are now operating normally as of Monday 11:00 AM PDT.

2. identifiedJul 20, 2026, 16:16 UTC

   We have identified the root cause and are adding additional resources to better handle the load. Currently affected components are Journeys, Event Streams, and Outbound Data Integrations.

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.

• Sentry: EU Region Error, Attachment, and Feedback latencyCritical · Jul 20, 2026, 11:11 UTC
• OVHcloud: [GLOBAL][Databases] - Database incident notificationMajor · Jul 20, 2026, 07:48 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
• Pinecone: [SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexesMinor · Jul 20, 2026, 16:44 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