OneSignal outage: Dashboard & API - Partial Outage

1. resolvedMay 11, 2026, 18:44 UTC

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

2. monitoringMay 11, 2026, 18:36 UTC

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 30 minutes.

3. investigatingMay 11, 2026, 17:55 UTC

   **What’s happening:** Some customers are unable to access the dashboard or API **Who’s affected:** • Customers with an app id starting with 2 **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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Upstash: Fly.io Upstash Redis service distruption (FRA region)Major · May 11, 2026, 15:05 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• ReadMe: Degraded performance across Admin HubsMinor · May 11, 2026, 15:43 UTC
• Akamai: Bot Manager Premier IssuesMinor · May 11, 2026, 16:03 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