outages.live
Live
ExpoIncident · 2026-09-21 21:18 UTC

Elevated rate of failed iOS submissions

ResolvedOfficial update

This incident has been resolved.

The latest update from Expo.

State

Resolved

Started

41 d ago

2026-09-21 21:18 UTC

Lasted

9 h 24 min

until 2026-09-22 06:42 UTC

Worst impact

Partial outage

Timeline

3 updates
21:1823:3902:0004:2106:42
Partial outageUpdate postedTimes in UTC

Identified

14 min 3%

Monitoring

9 h 10 min 97%

Updates

Times in UTC

As posted by Expo

Resolved2026-09-22 06:42 UTC

This incident has been resolved.

Monitoring2026-09-21 21:32 UTC

The errors from the 3rd party API have stopped. Submissions look healthy!

Identified2026-09-21 21:18 UTC

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

Affected components

4
EAS SubmitApple Developer APIsThird-Party Services - Apple Developer APIsExpo Application Services - EAS Submit

Expo in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

24

Median duration

2 h 34 min

This incident

3.7× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 h
median 2 h 34 min
90 days agoToday

Other Expo incidents

All incidents

Expo·Elevated submission error rates

This incident has been resolved.

Resolvedresolved 15 d ago

Expo·Elevated iOS submission error rates

This incident has been resolved.

Resolvedresolved 16 d ago

Expo·Elevated API server error rates affecting submissions and builds

This incident has been resolved.

Resolvedresolved 18 d ago

Expo·Website and services partially unavailable due to high database load

This incident has been resolved.

Resolvedresolved 27 d ago

Expo·EAS Update cache issue for rollout updates

This incident has been resolved.

Resolvedresolved 38 d ago

Follow Expo

Your coding agent knows when Expo is down, and tells you when a failure is theirs, not yours. You can also get Expo incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "expo" and tell me if Expo has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=expo
Slack
/feed subscribe https://outages.cc/feed.xml?providers=expo

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane