- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 1h 45m it lasted.
Anything that failed between 2026-08-04 15:31 UTC and 2026-08-04 17:15 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
- identified
We’re seeing intermittent template build failures caused by an upstream outage. Any build or sandbox command that installs packages via `apt` may intermittently fail or time out. Retries may succeed. Upstream status: [**https://status.canonical.com/**](https://status.canonical.com/#/) We’re monitoring and will update as it recovers.
provider
- resolved
Ubuntu package archive has recovered, and template builds and `apt` installs are working normally again. If you hit failures during the outage, please retry now or contact our support at support@e2b.dev. Thanks for your patience
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-2a5f574f96
Is E2B still down?
No, this incident was resolved 2026-08-04 17:15 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
1h 45m, from 2026-08-04 15:31 UTC to 2026-08-04 17:15 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.