Expo outage: Elevated rate of failed iOS submissions

Affected components

• Apple Developer APIs
• EAS Submit

1. resolvedSep 21, 2026, 20:41 UTC

   This incident has been resolved.

2. monitoringSep 21, 2026, 20:31 UTC

   It looks like the 3rd party API is healthy again. We're going to keep monitoring.

3. identifiedSep 21, 2026, 20:26 UTC

   We're seeing an elevated rate of iOS submissions failing. Our logs point to a failing App Store Connect API (502 bad gateway response status code).

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.

• Shippo: Axlehire tracking disruptionsMajor · Sep 20, 2026, 12:17 UTC
• Confluent Cloud: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2Major · Sep 21, 2026, 16:15 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Mobile Puerto RicoMinor · Sep 20, 2026, 17:47 UTC
• Twilio: Voice Call Post Dial Delay from Twilio Phone Numbers to Jazz PakistanMinor · Sep 21, 2026, 06:10 UTC
• Linode: Emerging Service Issue - Cloud Manager and APIMinor · Sep 21, 2026, 17:13 UTC
• Zoom: Service Degradation Affecting Apple Login for Zoom Sign-in.Minor · Sep 21, 2026, 18:17 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