OneSignal incident: Delay in deliveries impacting free customers

1. resolvedMay 22, 2026, 20:23 UTC

   The necessary mitigations have been applied and all systems are now operating normally.

2. identifiedMay 22, 2026, 19:46 UTC

   We've identified the root cause and are actively implementing mitigations.

3. investigatingMay 22, 2026, 19:37 UTC

   **What’s happening:** Timezone based and intelligent deliveries impacted because of backlog of messages. **Who’s affected:** • Any free customers using Timezone-based Delivery, Intelligent Delivery, or Retry Delivery. **Current Status:** We are investigating the issue and will provide an update in 30 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.

• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Snyk: Snyk Tests for Gradle projects DegradationMinor · May 22, 2026, 02:29 UTC
• Linode: Service Issue - Paris (FR-PAR3)Minor · May 22, 2026, 11:22 UTC
• Clerk: Issue with Provisioning DomainsMinor · May 22, 2026, 15:48 UTC
• Expo: EAS Update reduced availabilityMinor · May 22, 2026, 19:06 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