Template builds failing on Ubuntu package installs
E2B template builds that install Ubuntu packages with apt can fail. Template builds that do not install Ubuntu packages are not affected. Running sandboxes and sandbox creation are not affected. E2B has identified the issue: Ubuntu package servers are unreachable. E2B monitors the issue.
State
Identified
Started
Ongoing for
1 h 47 min
Worst impact
Degraded
Timeline
2 updatesIdentified
1 h 47 min 100%
Updates
Times in UTCAs posted by E2B
Some template builds are failing when they install packages with apt. Ubuntu's package servers ( ) are currently unreachable, so build steps that run apt-get update or apt-get install may fail. Running sandboxes and sandbox creation are not affected. If your build fails on an apt step, please retry it or wait once the upstream issue is resolved. Templates that don't install Ubuntu packages are expected to build normally. We're monitoring the issue and will post an update when builds are back to normal.
Some template builds are failing when they install packages with apt. Ubuntu's package servers ([security.ubuntu.com](http://security.ubuntu.com)) are currently unreachable, so build steps that run apt-get update or apt-get install may fail. Running sandboxes and sandbox creation are not affected. If your build fails on an apt step, please retry it or wait once the upstream issue is resolved. Templates that don't install Ubuntu packages are expected to build normally. We're monitoring the issue and will post an update when builds are back to normal.
E2B in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
1 h 34 min
This incident
About the median
Other E2B incidents
All incidents
E2B·Elevated 503 errors in EU-West-1
E2B reports elevated 503 errors in the EU-West-1 region. Other regions are not affected. E2B resolved the incident. Some requests failed from 15:01 to 15:35 UTC. The incident is resolved.
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.
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.live/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.live/feed.xml?providers=e2b/feed subscribe https://outages.live/feed.xml?providers=e2bFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane