- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, eu-west-1
- Down Index
- 26of 100
What to do
Check whether you use E2B in eu, eu-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 1h 27m it lasted.
Anything that failed between 2026-11-05 15:21 UTC and 2026-11-05 16:48 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're investigating elevated 503 errors affecting some requests in the EU-West-1 region. Other regions are not affected. We'll share an update as soon as we know more.
provider
- resolved
Between 15:01 and 15:40 UTC, some requests to EU-West-1 failed with 503 errors. Part of our edge gateway instances went down for a routine replacement, and the remaining ones couldn't keep up with the traffic. We added more capacity, and everything has been running normally since 15:40 UTC. We're sorry 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-a57676a3ea
Is E2B still down?
No, this incident was resolved 2026-11-05 16:48 UTC. For E2B's live state, see https://down.guide/e2b.
How long did it last?
1h 27m, from 2026-11-05 15:21 UTC to 2026-11-05 16:48 UTC, by the times E2B posted.
What was affected?
E2B named in eu, eu-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.