- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 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 0m it lasted.
Anything that failed between 2026-03-12 13:23 UTC and 2026-03-12 12:25 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 1
- resolved
Some workflow runs due to progress between 11:50 UTC and 12:25 UTC have failed to due to internal outage. Easiest mitigation is to cancel the frozen workflow and retry "from failed jobs". We are sorry for the disruption.
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-b5b69c0479
Is Expo still down?
No, this incident was resolved 2026-03-12 12:25 UTC. For Expo's live state, see https://down.guide/expo.
How long did it last?
0m, from 2026-03-12 13:23 UTC to 2026-03-12 12:25 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.