E2B: Elevated error rates for pause/connect/snapshot sandboxes on US cluster

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 1h 26m it lasted.
Anything that failed between 2026-07-22 06:48 UTC and 2026-07-22 08:14 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.

investigatingJul 22, 2026, 5:40 AM UTC
Investigating this
provider
identifiedJul 22, 2026, 6:30 AM UTC
We identified and resolved issue, now traffic should be recovering.
provider
monitoringJul 22, 2026, 6:50 AM UTC
Monitoring system recovery
provider
resolvedJul 22, 2026, 8:14 AM UTC
Resolved this
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is E2B still down?

No, this incident was resolved 2026-07-22 08:14 UTC. For E2B's live state, see https://down.guide/e2b.

How long did it last?

1h 26m, from 2026-07-22 06:48 UTC to 2026-07-22 08:14 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.