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

November 2026
Template builds failing on Ubuntu package installs
minor

View incident details and source

Notice published:

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

Template Builds Template Builds Template Builds Template Builds Template Builds
resolved
Ubuntu’s package servers are reachable again and template builds that install packages with apt are completing normally.
identified
Some template builds are failing when they install packages with apt. Ubuntu's package servers (https://status.canonical.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.
Elevated 503 errors in EU-West-1
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
Between 15:01 and 15:40 UTC, some requests to EU-West-1 failed with 503 errors. Part of our edge gateway instances went down for a routine replacement, and the remaining ones couldn't keep up with the traffic. We added more capacity, and everything has been running normally since 15:40 UTC. We're sorry for the disruption.
investigating
We're investigating elevated 503 errors affecting some requests in the EU-West-1 region. Other regions are not affected. We'll share an update as soon as we know more.
October 2026
Intermittent template build errors on US-West-1
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 fully resolved. We apologize for the disruption. If you are still seeing issues, please let us know.
investigating
We are investigating failures in template builds on US-West-1. Some builds fail when pulling a Docker Hub base image, with an "access denied" error, even though the image exists. Sandbox creation from existing templates is not affected. We will post updates as we learn more.
Degraded performance for sandbox operations on US-West-1
minor

View incident details and source

Notice published:

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

Template Builds Sandbox Pause/Resume/Create Persistent Volumes
resolved
The 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 you still see issues. We apologize for the disruption.
investigating
We are investigating degraded performance for sandbox operations on US-West-1. Some requests to create, pause or resume sandboxes may fail or take longer than usual. We will post updates as we learn more.
Template builds failing
major

View incident details and source

Notice published:

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

Template Builds Template Builds Template Builds Template Builds
resolved
Between 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 fixed. Template builds are working normally again. Running sandboxes were not affected. If a build failed during this window, please retry it. We apologize for any disruption.
identified
We have identified an issue causing new template builds to fail.
Increased errors on sandbox pause.
partial

View incident details and source

Notice published:

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

Sandbox Pause/Resume/Create
resolved
This incident has been resolved. Sandbox pause and resume are working normally.
identified
We’ve identified the issue and are scaling up capacity to mitigate.
investigating
We’re seeing increased errors on sandbox pause and resume and are investigating. We’re investigating the root cause and will post an update as soon as we know more.
September 2026
Elevated error rates when creating sandboxes from snapshots
partial

View incident details and source

Notice published:

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

Sandbox Pause/Resume/Create
resolved
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.
monitoring
We’ve deployed the fix, and sandbox creation from snapshots is operating normally. We’re continuing to monitor to confirm stability.
identified
We’ve confirmed the root cause and are working to deploy a fix. We’ll share another update once the fix is in place and we’ve verified recovery.
identified
Our investigation points to a compatibility issue affecting some snapshot restores. We’re validating these findings and working toward a resolution. We’ll share further updates as we learn more.
investigating
Some teams are experiencing elevated error rates when creating sandboxes from snapshots. Our team is investigating the root cause and will share updates as we learn more.
Elevated errors levels on US cluster from internal migration
partial

View incident details and source

Notice published:

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

Sandbox Network Traffic
resolved
All operations are fully recovered.
identified
During an internal migration operation, a subset of traffic on our US cluster started erroring. Impact peaked at ~15% error rate.
Elevated error rates and slower sandbox start times
partial

View incident details and source

Notice published:

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

Sandbox Pause/Resume/Create
resolved
This incident has been resolved. Sandbox creation and API error rates are back to normal. We apologize for the disruption.
monitoring
The service has recovered and API error rates are back to normal. We are keeping this incident in monitoring status to confirm full stability before we mark it resolved.
identified
We are still working to stabilize the affected infrastructure. API error rates have dropped and are continuing to recover. Our infrastructure team is actively working to bring all services fully back up. We will post another update shortly.
identified
We are still working on a fix for the elevated error rates and increased sandbox start times. A portion of sandbox creation requests are currently failing or taking longer than usual. Our team is scaling capacity to reduce the impact while we work toward a full resolution. We will post another update shortly.
identified
We are still working on a fix for the elevated error rates and increased sandbox start times. Our team is scaling capacity to reduce the impact while we work toward a full resolution. Some users may continue to see failed requests or slower sandbox creation.
identified
We have identified the cause of the elevated error rates and increased sandbox start times. Our team is working on a fix and we will post another update shortly.
Elevated error rates and slower sandbox start times
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
Sandbox start times and error rates have returned to normal and the incident is fully resolved.
identified
We have identified the cause of the elevated errors and resolved the issue. An internal caching layer is under heavy load due to an unusually high volume of running sandboxes, and our infra team is working on the fix.
investigating
We are currently investigating elevated error rates and increased sandbox start times. Some users may experience failed requests or slower-than-usual sandbox creation. Our team is actively working on it and we will post an update shortly.
Get alerts for E2B Subscribe to the provider incident feed Browse all services