Skip to main content
Expo

High queue times for Android and iOS builds

Degraded Lasted 9h 45m · started · Expo's page

Level
confirmed
Worst impact
Degraded
Components
EAS Build
Down Index
38of 100

What to do

  • Check whether you use Expo EAS Build. 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 9h 45m it lasted.

    Anything that failed between 2026-05-15 07:15 UTC and 2026-05-15 17:00 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

    Users with Android Builds on priority queues may experience extended wait times as we hit capacity

    provider

  2. monitoring

    Android priority queue times have returned to normal levels and backlogged jobs are progressing. We are continuing to monitor performance.

    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-95d9d0097a

Is Expo still down?

No, this incident was resolved 2026-05-15 17:00 UTC. For Expo's live state, see https://down.guide/expo.

How long did it last?

9h 45m, from 2026-05-15 07:15 UTC to 2026-05-15 17:00 UTC, by the times Expo posted.

What was affected?

Expo named EAS Build.

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.