- Level
- confirmed
- Worst impact
- Degraded
- Components
- npm Package installation
- Down Index
- 38of 100
What to do
Check whether you use Expo npm Package installation. 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 18h it lasted.
Anything that failed between 2026-09-03 22:45 UTC and 2026-09-04 16:45 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 2
- investigating
We are currently monitoring degraded performance on the NPM registry. The degradation may cause package installs to time out, and EAS Builds to fail when using NPM. We will provide updates from NPM when available.
provider
- resolved
This incident has been resolved. NPM has restored registry performance. Package installs and EAS Builds using NPM should now complete as expected.
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-28a78be791
Is Expo still down?
No, this incident was resolved 2026-09-04 16:45 UTC. For Expo's live state, see https://down.guide/expo.
How long did it last?
18h, from 2026-09-03 22:45 UTC to 2026-09-04 16:45 UTC, by the times Expo posted.
What was affected?
Expo named npm Package installation.
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.