- Level
- confirmed
- Worst impact
- Degraded
- Components
- EAS Workflows
- Down Index
- 34of 100
What to do
Check whether you use Expo 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 2h 31m it lasted.
Anything that failed between 2026-08-14 17:04 UTC and 2026-08-14 19:35 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 6
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
`eas-cli@21.8.0` package set to `latest` in the meantime. working on fix and will publish a new version.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
Fix deployed to server, `eas-cli@22.0.0` set back to `latest`.
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-0b8bf7a180
Is Expo still down?
No, this incident was resolved 2026-08-14 19:35 UTC. For Expo's live state, see https://down.guide/expo.
How long did it last?
2h 31m, from 2026-08-14 17:04 UTC to 2026-08-14 19:35 UTC, by the times Expo posted.
What was affected?
Expo named 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.