- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 30of 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 0m it lasted.
Anything that failed between 2026-10-21 14:40 UTC and 2026-10-21 14:06 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
This was caused by a configuration issue on our side, which has been fixed.Read the postmortem
Updates from E2B 2
- identified
We have identified an issue causing new template builds to fail.
provider
- resolved
Between 14:03 and 14:06 UTC on October 21, new template builds failed to start with the error “500: invalid build configuration, contact support”. This was caused by a configuration issue on our side, which has been fixed. Template builds are working normally again. Running sandboxes were not affected. If a build failed during this window, please retry it. We apologize for any 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-88607c7f5b
Is E2B still down?
No, this incident was resolved 2026-10-21 14:06 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
0m, from 2026-10-21 14:40 UTC to 2026-10-21 14:06 UTC, by the times E2B posted.
What caused it?
E2B wrote: "This was caused by a configuration issue on our side, which has been fixed." The postmortem: https://status.e2b.dev/incidents/01M5FEGC218X1EEYP1V962EMQW
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.