Elevated 503 errors in EU-West-1
E2B reported elevated 503 errors on some requests in the EU-West-1 region. Other regions were not affected. E2B states that the incident is resolved, and it lasted 87 minutes.
State
Resolved
Started
Lasted
1 h 27 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 27 min 100%
Updates
Times in UTCAs posted by E2B
Between 15:01 and 15:35 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.
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.
E2B in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
9
Median duration
1 h 34 min
This incident
About the median
Other E2B incidents
All incidents
E2B·Intermittent template build errors on US-West-1
The issue has been fully resolved. We apologize for the disruption. If you are still seeing issues, please let us know.
E2B·Increased errors on sandbox pause.
This incident has been resolved. Sandbox pause and resume are working normally.
E2B·Elevated error rates when creating sandboxes from snapshots
This incident has been fully resolved. We’ll publish a postmortem soon with more details on the cause and resolution. We apologize again for the disruption.
E2B·Elevated error rates and slower sandbox start times
This incident has been resolved. Sandbox creation and API error rates are back to normal. We apologize for the disruption.
E2B·Elevated error rates and slower sandbox start times
Sandbox start times and error rates have returned to normal and the incident is fully resolved.
Follow E2B
Your coding agent knows when E2B is down, and tells you when a failure is theirs, not yours. You can also get E2B incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "e2b" and tell me if E2B has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=e2b/feed subscribe https://outages.cc/feed.xml?providers=e2bFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane