- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-west-1
- Down Index
- 16of 100
What to do
Check whether you use E2B in us, us-west-1. 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-27 11:27 UTC and 2026-10-27 10:57 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
- investigating
We are investigating degraded performance for sandbox operations on US-West-1. Some requests to create, pause or resume sandboxes may fail or take longer than usual. We will post updates as we learn more.
provider
- resolved
The issue has been resolved, and sandbox operations on US-West-1 are back to normal. If a request failed during this window, please retry it or contact our support team at [support@e2b.dev](mailto:support@e2b.dev) if you still see issues. We apologize for the 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-36074196da
Is E2B still down?
No, this incident was resolved 2026-10-27 10:57 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
0m, from 2026-10-27 11:27 UTC to 2026-10-27 10:57 UTC, by the times E2B posted.
What was affected?
E2B named in us, us-west-1.
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.