Skip to main content
Expo

Elevated rate of failed iOS submissions

Partial outage Lasted 14m · started · Expo's page

Level
confirmed
Worst impact
Partial outage
Components
EAS Submit, Apple Developer APIs
Down Index
39of 100

What to do

  • Check whether you use Expo EAS Submit, Apple Developer APIs. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 14m it lasted.

    Anything that failed between 2026-09-21 20:26 UTC and 2026-09-21 20:41 UTC may need a replay.
  • Subscribe to Expo's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=expo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Expo 3

  1. identified

    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).

    provider

  2. monitoring

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

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-1012cbfdec

Is Expo still down?

No, this incident was resolved 2026-09-21 20:41 UTC. For Expo's live state, see https://down.guide/expo.

How long did it last?

14m, from 2026-09-21 20:26 UTC to 2026-09-21 20:41 UTC, by the times Expo posted.

What was affected?

Expo named EAS Submit, Apple Developer APIs.

What caused it?

Expo hasn't published a root cause. If it does, it shows here.

Where does this come from?

Expo's official status page, https://status.expo.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.