outages.live
Live
E2B logo

E2B

E2B is operational

Checked 15 s ago Operational

History

90 days agoToday

Incidents in 90 days

11

Days with an incident

9

Median duration

1 h 41 min

Longest incident

4 h 45 min

Components

19
Sandbox Pause/Resume/Create Operational
90 days agoNo incidentsToday
Sandbox Network Traffic Operational
90 days agoNo incidentsToday
Persistent Volumes Operational
90 days agoNo incidentsToday
Template Builds Operational
90 days agoNo incidentsToday
Sandbox Pause/Resume/Create Operational
90 days agoNo incidentsToday
Sandbox Network Traffic Operational
90 days agoNo incidentsToday
Template Builds Operational
90 days agoNo incidentsToday
Persistent Volumes Operational
90 days agoNo incidentsToday
Sandbox Pause/Resume/Create Operational
90 days agoNo incidentsToday
Sandbox Network Traffic Operational
90 days agoNo incidentsToday
Persistent Volumes Operational
90 days agoNo incidentsToday
Template Builds Operational
90 days agoNo incidentsToday
Sandbox Pause/Resume/Create Operational
90 days agoNo incidentsToday
Sandbox Network Traffic Operational
90 days agoNo incidentsToday
Persistent Volumes Operational
90 days agoNo incidentsToday
Template Builds Operational
90 days agoNo incidentsToday
Landing Page Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Documentation Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration1 h 21 min09:59 to 11:19Intermittent template build errors on US-West-1Degraded

The issue has been fully resolved. We apologize for the disruption. If you are still seeing issues, please let us know.

Oct 2, 2026

Duration24 min19:34 to 19:58Increased errors on sandbox pause.Partial outage

This incident has been resolved. Sandbox pause and resume are working normally.

Sep 15, 2026

Duration4 h 45 min16:53 to 21:38Elevated error rates when creating sandboxes from snapshotsPartial outage

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.

Sep 3, 2026

Duration1 h 41 min01:21 to 03:02Elevated error rates and slower sandbox start timesPartial outage

This incident has been resolved. Sandbox creation and API error rates are back to normal. We apologize for the disruption.

Duration15 min00:02 to 00:18Elevated error rates and slower sandbox start timesDegraded

Sandbox start times and error rates have returned to normal and the incident is fully resolved.

Sep 1, 2026

Duration3 h 1 min18:37 to 21:38Elevated template build failuresDegraded

The build failures have been resolved.

Aug 27, 2026

Duration2 h 21 min14:50 to 17:11Increased error rate for pause/resume operations on US clusterDegraded

The issue has been resolved and the service is back to normal. Please reach out to our support if you experience any further issues.

Aug 21, 2026

Duration9 min23:17 to 23:26EU region sandbox traffic connection issuesPartial outage

The issue affecting sandbox traffic connections in the EU region has now been resolved. A fix has been deployed and network traffic operating normally. Thank you for your patience.

Aug 20, 2026

Duration4 h 3 min16:25 to 20:27Elevated error rates for sandbox operationsDegraded

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.

Aug 5, 2026

Duration9 min00:08 to 00:17Volumes content inaccessible outside of sandboxPartial outage

The issue affecting volume content access outside of sandboxes has been resolved. A domain configuration mismatch was causing authorization errors when customers attempted to read or write files directly through our volume API without using a sandbox. We apologize for the disruption this caused. If you continue to experience any issues accessing your volumes, please contact our support team.

Aug 4, 2026

Duration1 h 45 min15:31 to 17:15Template build failures - upstream Ubuntu (apt) outageDegraded

Ubuntu package archive has recovered, and template builds and `apt` installs are working normally again. If you hit failures during the outage, please retry now or contact our support at support@e2b.dev. Thanks for your patience

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=e2b
Slack
/feed subscribe https://outages.live/feed.xml?providers=e2b

Go from tracking outages to fixing production issues with Polylane.

Try Polylane