New Multi-region uptime checks and custom-domain status pages

E2B Outage History

Daily provider-status observations and published incident history for E2B.

Operational

E2B is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow E2B for future changes.

92.2% of 51 verified observed days had no reported provider issue

90-Day Trend

Sep 26Nov 15

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
October 2026 93.5% 31 2

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Daily Status (Last 51 Days)

Sep 26 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Elevated template build failures
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Template Builds
resolved
The build failures have been resolved.
investigating
We are investigating an elevated rate of template build failures. Some builds may fail or run slowly while we work on it.
investigating
We are investigating an elevated rate of template build failures. Some builds may fail or run slowly while we work on it.
August 2026
Intermittent template build failures
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Template Builds
resolved
The 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.
monitoring
We corrected the configuration and restored the affected build infrastructure. We are monitoring template-build error rates as the service recovers.
identified
We identified an incorrect configuration on newly started template-build infrastructure. This caused some builds to fail before execution began. We are applying a fix.
investigating
We are investigating intermittent failures affecting some template builds. Failed builds may return an internal error. Retrying may succeed.
Increased error rate for pause/resume operations on US cluster
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Sandbox Pause/Resume/Create
resolved
The issue has been resolved and the service is back to normal. Please reach out to our support if you experience any further issues.
monitoring
We have deployed a fix, and the error rates should be returning to normal. We will continue to monitor the situation.
investigating
We are investigating an increased error rate for pause/resume operations. We will post updates as we learn more.
Increased error rate when connecting to paused sandboxes
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Sandbox Pause/Resume/Create
resolved
A 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 running were not affected, no sandbox data was lost, and any request that failed will succeed on retry. The EU and APAC regions were not affected. If you are still seeing failures, please contact support@e2b.dev: mailto:support@e2b.dev. We apologize for the disruption.
investigating
We are investigating an increased error rate when connecting to paused sandboxes. Running sandboxes are not affected.
EU region sandbox traffic connection issues
partial

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Sandbox Network Traffic Sandbox Pause/Resume/Create
resolved
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.
monitoring
We are continuing to work on the issue affecting sandbox traffic connections. We have deployed a fix and the service is now recovering. We are monitoring closely and will post a final update once it is fully resolved.
identified
We are seeing an issue affecting sandbox traffic connections in the EU region. We are working on a fix and will post an update as soon as we have more information.
Elevated error rates for sandbox operations
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Sandbox Pause/Resume/Create
resolved
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.
monitoring
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.
monitoring
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.
monitoring
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
monitoring
Service is recovering. Sandbox operations are stabilizing and error rates are returning to normal. We continue to monitor closely.
investigating
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
investigating
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.
Volumes content inaccessible outside of sandbox
partial

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Persistent Volumes
resolved
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.
identified
We are currently investigating an issue affecting volume content access outside of sandboxes. Customers using our volume feature to read and write files directly (without going through a sandbox) may experience authorization errors. Our team identified a domain configuration mismatch that was introduced in a recent deployment and is working on a fix. We expect to have this resolved shortly. We apologize for any disruption this may cause. If you're experiencing issues accessing your volumes, please reach out to our support team and we'll be happy to assist.
Template build failures - upstream Ubuntu (apt) outage
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Template Builds Template Builds
resolved
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
identified
We’re seeing intermittent template build failures caused by an upstream outage. Any build or sandbox command that installs packages via apt may intermittently fail or time out. Retries may succeed. Upstream status: https://status.canonical.com/: https://status.canonical.com/#/ We’re monitoring and will update as it recovers.
July 2026
High demand caused resource exhaustion
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Sandbox Pause/Resume/Create
resolved
Cluster capacity is sufficient, and we are continuing monitoring the situation.
monitoring
Monitoring cluster recovery from exhaustion
Stripe services are degrading, which will affects the team and billing management
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Dashboard
resolved
We identified and recovered affected data. No customer operation impacted.
identified
Stripe backend looks degrading, we are investigating affected components.