Expo incident: Android Push Notifications Experiencing Delays

Affected components

• Push Notifications Broker

1. resolvedMay 14, 2026, 05:53 UTC

   This Incident has been resolved and services are operating normally again.

2. investigatingMay 14, 2026, 05:39 UTC

   We are currently investigating delays affecting Android push notification delivery. Our team is actively working to mitigate the issue and restore normal performance.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Expo'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.

• Confluence: Users experiencing issues accessing multiple Atlassian productsCritical · May 14, 2026, 04:54 UTC
• Bitbucket: Users experiencing issues accessing multiple Atlassian productsCritical · May 14, 2026, 05:03 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC

How often does Expo have incidents?

Expo reported 27 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See Expo's uptime and incident history