- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 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 15m it lasted.
Anything that failed between 2026-09-03 00:02 UTC and 2026-09-03 00:18 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 3
- investigating
We are currently investigating elevated error rates and increased sandbox start times. Some users may experience failed requests or slower-than-usual sandbox creation. Our team is actively working on it and we will post an update shortly.
provider
- identified
We have identified the cause of the elevated errors and resolved the issue. An internal caching layer is under heavy load due to an unusually high volume of running sandboxes, and our infra team is working on the fix.
provider
- resolved
Sandbox start times and error rates have returned to normal and the incident is fully resolved.
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-5fe5b48bf3
Is E2B still down?
No, this incident was resolved 2026-09-03 00:18 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
15m, from 2026-09-03 00:02 UTC to 2026-09-03 00:18 UTC, by the times E2B posted.
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.