Skip to main content
Expo

Elevated queue times for high-priority EAS iOS submissions

Degraded Lasted 2h 13m · started · Expo's page

Level
confirmed
Worst impact
Degraded
Components
EAS Submit
Down Index
34of 100

What to do

  • Check whether you use Expo EAS Submit. 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 2h 13m it lasted.

    Anything that failed between 2026-06-10 22:51 UTC and 2026-06-11 01:04 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. investigating

    We are investigating elevated queue times for iOS submissions on EAS Submit.

    provider

  2. monitoring

    EAS iOS submission queue times are returning to normal. We are actively monitoring to confirm full recovery and will provide an update once resolved.

    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-3d0ee969fb

Is Expo still down?

No, this incident was resolved 2026-06-11 01:04 UTC. For Expo's live state, see https://down.guide/expo.

How long did it last?

2h 13m, from 2026-06-10 22:51 UTC to 2026-06-11 01:04 UTC, by the times Expo posted.

What was affected?

Expo named EAS Submit.

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.