Elevated error rates for sandbox operations
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.
The latest update from E2B.
State
Resolved
Started
73 d ago
2026-08-20 16:25 UTC
Lasted
4 h 3 min
until 2026-08-20 20:27 UTC
Worst impact
Degraded
Timeline
7 updatesInvestigating
59 min 24%
Monitoring
3 h 4 min 76%
Updates
Times in UTCAs posted by E2B
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.
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.
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.
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
Service is recovering. Sandbox operations are stabilizing and error rates are returning to normal. We continue to monitor closely.
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
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.
E2B in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
1 h 41 min
This incident
2.4× 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