Skip to main content
Expo

Workflows impacted by NPM install timeouts and failures

Degraded Lasted 2h 21m · started · Expo's page

Level
confirmed
Worst impact
Degraded
Components
EAS Build, EAS Workflows
Down Index
34of 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 2h 21m it lasted.

    Anything that failed between 2026-06-16 16:31 UTC and 2026-06-16 18:53 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

  1. identified

    We have observed a degradation in our NPM cache that has resulted in Workflows to timeout and fail on npm install. The cache is now disabled.

    provider

  2. identified

    We are continuing to work on a fix for this issue.

    provider

  3. 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-e9b9b562dd

Is Expo still down?

No, this incident was resolved 2026-06-16 18:53 UTC. For Expo's live state, see https://down.guide/expo.

How long did it last?

2h 21m, from 2026-06-16 16:31 UTC to 2026-06-16 18:53 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.