- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 47of 100
What to do
Check whether your product depends on Expo. 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 15h 4m it lasted.
Anything that failed between 2026-09-04 16:05 UTC and 2026-09-05 07:10 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 4
- identified
Queue times for Android builds and other Linux workflows are currently elevated due to GCP regional capacity constraints. We are currently enabling capacity in additional regions. Jobs in queue are continuing to progress.
provider
- identified
Queue times for Android builds and other Linux workflows are currently elevated due to upstream provider issues affecting the provisioning of VM's. GCP has confirmed the issue and is working on resolving.
provider
- monitoring
The upstream issue with creating VM's has been resolved by GCP, Linux worker queues are draining, and queue times are returning to expected levels.
provider
- 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-6292467a78
Is Expo still down?
No, this incident was resolved 2026-09-05 07:10 UTC. For Expo's live state, see https://down.guide/expo.
How long did it last?
15h 4m, from 2026-09-04 16:05 UTC to 2026-09-05 07:10 UTC, by the times Expo posted.
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.