E2B Outage History

39 incidents recorded over the last 365 days, 39 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live E2B status100.00% uptime history

Every Recorded E2B Incident

E2B incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Intermittent template build errors on US-West-1The issue has been fully resolved. We apologize for the disruption. If you are still seeing issues, please let us know.1h 20mResolved
Oct 27, 2026Degraded performance for sandbox operations on US-West-1The issue has been resolved, and sandbox operations on US-West-1 are back to normal. If a request failed during this window, please retry it or contact our support team at [support@e2b.dev](mailto:support@e2b.dev) if…-30 minResolved
Oct 21, 2026Template builds failingBetween 14:03 and 14:06 UTC on October 21, new template builds failed to start with the error “500: invalid build configuration, contact support”. This was caused by a configuration issue on our side, which has been…-34 minResolved
Oct 2, 2026Increased errors on sandbox pause.This incident has been resolved. Sandbox pause and resume are working normally.23 minResolved
Sep 15, 2026Elevated error rates when creating sandboxes from snapshotsThis 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.4h 44mResolved
Sep 4, 2026Elevated errors levels on US cluster from internal migrationAll operations are fully recovered.-30 minResolved
Sep 3, 2026Elevated error rates and slower sandbox start timesThis incident has been resolved. Sandbox creation and API error rates are back to normal. We apologize for the disruption.1h 40mResolved
Sep 3, 2026Elevated error rates and slower sandbox start timesSandbox start times and error rates have returned to normal and the incident is fully resolved.15 minResolved
Sep 1, 2026Elevated template build failuresThe build failures have been resolved.3h 0mResolved
Sep 1, 2026Intermittent template build failuresThe issue has been resolved, and template builds are operating normally. Builds that failed during the outage can now be retried. We apologize for the inconvenience.-718 minResolved
Aug 27, 2026Increased error rate for pause/resume operations on US clusterThe issue has been resolved and the service is back to normal. Please reach out to our support if you experience any further issues.2h 21mResolved
Aug 25, 2026Increased error rate when connecting to paused sandboxesA configuration change on our side caused elevated 503 errors when connecting to paused sandboxes in the US region. We reverted the change, and error rates returned to normal at 12:32 UTC. Sandboxes that were already…-88 minResolved
Aug 21, 2026EU region sandbox traffic connection issuesThe 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.8 minResolved
Aug 20, 2026Elevated error rates for sandbox operationsResolved. 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.4h 2mResolved
Aug 5, 2026Volumes content inaccessible outside of sandboxThe 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…8 minResolved
Aug 4, 2026Template build failures - upstream Ubuntu (apt) outageUbuntu 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…1h 44mResolved
Jul 24, 2026High demand caused resource exhaustionCluster capacity is sufficient, and we are continuing monitoring the situation.16 minResolved
Jul 24, 2026Stripe services are degrading, which will affects the team and billing managementWe identified and recovered affected data. No customer operation impacted.1h 56mResolved
Jul 23, 2026Elevated error rates for pause sandboxes on US clusterResolved this3h 1mResolved
Jul 22, 2026Elevated error rates for pause/connect/snapshot sandboxes on US clusterResolved this1h 25mResolved
Jul 16, 2026Dashboard auth not functioningIssue confirmed by our auth provider, waiting for root cause. A configuration update caused some legitimate authentication-related requests to be incorrectly blocked.3 minResolved
Jul 1, 2026EU cluster degradationThe issue has been resolved, and all services are operating normally.3h 29mResolved
Jun 29, 2026Elevated error rates for resuming/creating sandboxes on EU clusterThe situation has been fully resolved, and the EU cluster is fully operational again. We apologize again for the inconvenience.-74 minResolved
Jun 25, 2026Investigating 503 status code on API Production components are fully available.18 minResolved
Jun 15, 2026Authentication DegradedThe issue affecting sign up and login has been resolved. All authentication services are operating normally. We apologize for the disruption and will share a full write-up shortly.1h 0mResolved
Jun 2, 2026Intermittent volume request timeoutsThe infrastructure improvements have resolved the issue.487h 16mResolved
Jun 2, 2026Degraded sandbox creationThe situation has been resolved. Please reach out if you encounter any errors going forward.3h 48mResolved
Jun 2, 2026Degraded sandbox creationThe issue has been resolved, and the cluster is fully operational again. Please let us know if you continue to experience any issues.3h 36mResolved
May 28, 2026Degraded sandbox creationThe issue has been fully resolved. Everything should be back to normal.-151 minResolved
May 13, 2026Elevated error rates for spawning sandboxesThe issue has been resolved, and everything is back to normal.-6 minResolved
May 4, 2026Initial status page updateInitial status page update-703916 minResolved
May 4, 2026Sandbox pause/resume degradedThe sandbox management should be fully working now.-36530 minResolved
May 4, 2026Package Installation DelaysThe issue has been resolved.-23823 minResolved
May 4, 2026Temporary Usage Spike and API ErrorsWe identified and resolved an issue that caused a temporary spike in reported usage for some teams, which may have resulted in billing limit errors. Systems are now operating normally.-10760 minResolved
May 4, 2026EU region degradationThe issue has been resolved-19200 minResolved
May 4, 2026Old template sandboxes might experience timeoutsEverything is operational again.-66268 minResolved
May 4, 2026Sandbox pause/resume degradedThe sandbox management should be fully working now.-71482 minResolved
May 4, 2026Sandbox management degradedThe issue has been resolved.-75284 minResolved
May 4, 2026Sandbox management degradedThe sandbox management should be fully working now.-80507 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next E2B incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This E2B Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before E2B acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single E2B outage in this window ran 20d 7h, against a mean recovery of 23h 54m. If you depend on E2B in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.