- Level
- confirmed
- Worst impact
- Degraded
- Regions
- apac, eu, us
- Down Index
- 20of 100
What to do
Check whether you use E2B in apac, eu, 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-08-25 14:00 UTC and 2026-08-25 12:32 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
- investigating
We are investigating an increased error rate when connecting to paused sandboxes. Running sandboxes are not affected.
provider
- resolved
A configuration change on our side caused elevated 503 errors when connecting to paused sandboxes in the US region. We reverted the change, and error rates returned to normal at 12:32 UTC. Sandboxes that were already running were not affected, no sandbox data was lost, and any request that failed will succeed on retry. The EU and APAC regions were not affected. If you are still seeing failures, please contact [support@e2b.dev](mailto:support@e2b.dev). We apologize for the disruption.
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-029c5b871c
Is E2B still down?
No, this incident was resolved 2026-08-25 12:32 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
0m, from 2026-08-25 14:00 UTC to 2026-08-25 12:32 UTC, by the times E2B posted.
What was affected?
E2B named in apac, eu, 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.