- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 25of 100
What to do
Check whether your product depends on E2B. 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 24m it lasted.
Anything that failed between 2026-10-02 19:34 UTC and 2026-10-02 19:58 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.
Root cause
We’re investigating the root cause and will post an update as soon as we know more.Read the postmortem
Updates from E2B 3
- investigating
We’re seeing increased errors on sandbox pause and resume and are investigating. We’re investigating the root cause and will post an update as soon as we know more.
provider
- identified
We’ve identified the issue and are scaling up capacity to mitigate.
provider
- resolved
This incident has been resolved. Sandbox pause and resume are working normally.
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-c294cff739
Is E2B still down?
No, this incident was resolved 2026-10-02 19:58 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
24m, from 2026-10-02 19:34 UTC to 2026-10-02 19:58 UTC, by the times E2B posted.
What caused it?
E2B wrote: "We’re investigating the root cause and will post an update as soon as we know more." The postmortem: https://status.e2b.dev/incidents/01M3Z1REMPVT6R56J86PR3K2HS
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.