- Level
- confirmed
- Worst impact
- Degraded
- Components
- EAS Build, EAS Workflows
- Down Index
- 30of 100
What to do
Check whether you use Expo EAS Build, EAS Workflows. 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 21m it lasted.
Anything that failed between 2026-09-02 21:44 UTC and 2026-09-02 22:05 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
- investigating
Queue times are elevated for Linux workers for EAS Build and Workflows. Android build jobs may be delayed. We are currently investigating the issue.
provider
- identified
We have determined that some of our package caches are under high load, and this is causing elevated build times and in turn causing higher Linux worker queue times. We are currently working on a fix. In-progress builds are continuing to complete and enqueued builds are continuing to be processed.
provider
- resolved
A fix was deployed at 2:50pm PT/5:50pm ET. The job queue has been running as expected. The root cause of this incident is that a new version of a cache needed more vCPUs than it was given, and we have increased the CPU count as the immediate fix along with additional monitoring for CPU usage on these cache instances.
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-656b680f6c
Is Expo still down?
No, this incident was resolved 2026-09-02 22:05 UTC. For Expo's live state, see https://down.guide/expo.
How long did it last?
21m, from 2026-09-02 21:44 UTC to 2026-09-02 22:05 UTC, by the times Expo posted.
What was affected?
Expo named EAS Build, EAS Workflows.
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.