Skip to main content
E2B

Elevated errors levels on US cluster from internal migration

Partial outage Lasted 0m · started · E2B's page

Level
confirmed
Worst impact
Partial outage
Regions
us
Down Index
22of 100

What to do

  • Check whether you use E2B in us. 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-09-04 19:16 UTC and 2026-09-04 18:46 UTC may need a replay.
  • Subscribe to E2B's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=e2b works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from E2B 2

  1. identified

    During an internal migration operation, a subset of traffic on our US cluster started erroring. Impact peaked at ~15% error rate.

    provider

  2. resolved

    All operations are fully recovered.

    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-be84cef7fc

Is E2B still down?

No, this incident was resolved 2026-09-04 18:46 UTC. For E2B's live state, see https://down.guide/e2b.

How long did it last?

0m, from 2026-09-04 19:16 UTC to 2026-09-04 18:46 UTC, by the times E2B posted.

What was affected?

E2B named in us.

What caused it?

E2B hasn't published a root cause. If it does, it shows here.

Where does this come from?

E2B's official status page, https://status.e2b.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.