- Level
- confirmed
- Worst impact
- Major outage
- Regions
- us
- Down Index
- 41of 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 19m it lasted.
Anything that failed between 2026-06-25 03:33 UTC and 2026-06-25 03:52 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 5
- investigating
We're currently observing elevated 503 errors impacting the US cluster. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible.
provider
- investigating
Sandbox create in US Region is impacted
provider
- monitoring
Reverted a recent production change on API side. Monitoring recovery. Dashboard is still currently unavailable.
provider
- monitoring
Full revert of production change is complete. Service is fully operational.
provider
- resolved
Production components are fully available.
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-07395b39e6
Is E2B still down?
No, this incident was resolved 2026-06-25 03:52 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
19m, from 2026-06-25 03:33 UTC to 2026-06-25 03:52 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.