Skip to main content
Expo

Free plan users are getting capped on builds before reaching allowance

Degraded Lasted 55m · started · Expo's page

Level
confirmed
Worst impact
Degraded
Components
EAS Build
Down Index
32of 100

What to do

  • Check whether you use Expo EAS Build. 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 55m it lasted.

    Anything that failed between 2026-07-01 13:39 UTC and 2026-07-01 14: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 2

  1. investigating

    We are investigating reports that some free plan users are getting limited on builds before reaching their included allowance.

    provider

  2. resolved

    It looks like users are not actually getting limited, but are getting a 100% build used warning ahead of time when triggering a build from the eas cli. Use eas-cli@latest for correct messaging.

    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-2fb904533f

Is Expo still down?

No, this incident was resolved 2026-07-01 14:35 UTC. For Expo's live state, see https://down.guide/expo.

How long did it last?

55m, from 2026-07-01 13:39 UTC to 2026-07-01 14:35 UTC, by the times Expo posted.

What was affected?

Expo named EAS Build.

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.