- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 25of 100
What to do
Check whether you use E2B in 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 4h 3m it lasted.
Anything that failed between 2026-08-20 16:25 UTC and 2026-08-20 20:27 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 7
- investigating
We are experiencing elevated error rates for sandbox operations. The team is investigating the root cause, and we will keep you updated as we learn more. We apologize for the inconvenience.
provider
- investigating
We are investigating increased error rates for sandbox operations. Start times are slower than usual, and a small number of sandbox resumes (under 1%) are affected. Adding retries to your sandbox operations can help mitigate the impact while we work on a fix
provider
- monitoring
Service is recovering. Sandbox operations are stabilizing and error rates are returning to normal. We continue to monitor closely.
provider
- monitoring
We’ve identified the issue as related to an ongoing incident with one of our upstream providers. We’re monitoring their recovery and its impact on our service. Upstream incident: https://status.cloud.google.com/incidents/utF3FMFdQfwBzJcGG6vf
provider
- monitoring
We are no longer seeing customer impact from the earlier Google Cloud Compute Engine incident. Sandbox create, pause, and resume in the US region have returned to normal. We are keeping this incident open and monitoring to confirm stability before marking it resolved.
provider
- monitoring
We no longer see any impact on our customers. Sandbox create, pause, and resume in the US region are operating normally. This incident remains in monitoring while we wait for Google Cloud to fully resolve the underlying Compute Engine issue. We will post a final update once that is confirmed.
provider
- resolved
Resolved. Google Cloud fully resolved the underlying Compute Engine incident at 12:37 PDT and all sandbox operations in the US region are back to normal.
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-b2eb9023ae
Is E2B still down?
No, this incident was resolved 2026-08-20 20:27 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
4h 3m, from 2026-08-20 16:25 UTC to 2026-08-20 20:27 UTC, by the times E2B posted.
What was affected?
E2B named in 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.