Is E2B down right now?

No, it is up

Operational · All systems operational

Checked 5 min ago. In this state since 4 Nov 2026, 03:18 UTC. Source: status.e2b.dev

Components

  • US-West-1 · Sandbox Pause/Resume/CreateOperational
  • US-West-1 · Sandbox Network TrafficOperational
  • US-West-1 · Persistent VolumesOperational
  • US-West-1 · Template BuildsOperational
  • US-West-2 · Sandbox Pause/Resume/CreateOperational
  • US-West-2 · Sandbox Network TrafficOperational
  • US-West-2 · Template BuildsOperational
  • US-West-2 · Persistent VolumesOperational
  • US-East-1 · Sandbox Pause/Resume/CreateOperational
  • US-East-1 · Sandbox Network TrafficOperational
  • US-East-1 · Template BuildsOperational
  • US-East-1 · Persistent VolumesOperational
  • EU-West-1 · Sandbox Pause/Resume/CreateOperational
  • EU-West-1 · Sandbox Network TrafficOperational
  • EU-West-1 · Persistent VolumesOperational
  • EU-West-1 · Template BuildsOperational
  • AP-Southeast-1 · Sandbox Pause/Resume/CreateOperational
  • AP-Southeast-1 · Sandbox Network TrafficOperational
  • AP-Southeast-1 · Persistent VolumesOperational
  • AP-Southeast-1 · Template BuildsOperational
  • Global · Landing PageOperational
  • Global · DashboardOperational
  • Global · DocumentationOperational

User reports

Having trouble with E2B? Reports are anonymous and only counted, no cookies.

24 h ago0 reports in the last 24 hNow

E2B uptime, last 90 days

2026-08-07: no data 2026-08-08: no data 2026-08-09: no data 2026-08-10: no data 2026-08-11: no data 2026-08-12: no data 2026-08-13: no data 2026-08-14: no data 2026-08-15: no data 2026-08-16: no data 2026-08-17: no data 2026-08-18: no data 2026-08-19: no data 2026-08-20: no data 2026-08-21: no data 2026-08-22: no data 2026-08-23: no data 2026-08-24: no data 2026-08-25: no data 2026-08-26: no data 2026-08-27: no data 2026-08-28: no data 2026-08-29: no data 2026-08-30: no data 2026-08-31: no data 2026-09-01: no data 2026-09-02: no data 2026-09-03: no data 2026-09-04: no data 2026-09-05: no data 2026-09-06: no data 2026-09-07: no data 2026-09-08: no data 2026-09-09: no data 2026-09-10: no data 2026-09-11: no data 2026-09-12: no data 2026-09-13: no data 2026-09-14: no data 2026-09-15: no data 2026-09-16: no data 2026-09-17: no data 2026-09-18: no data 2026-09-19: no data 2026-09-20: no data 2026-09-21: no data 2026-09-22: no data 2026-09-23: no data 2026-09-24: no data 2026-09-25: no data 2026-09-26: no data 2026-09-27: no data 2026-09-28: no data 2026-09-29: no data 2026-09-30: no data 2026-10-01: no data 2026-10-02: no data 2026-10-03: no data 2026-10-04: no data 2026-10-05: no data 2026-10-06: no data 2026-10-07: no data 2026-10-08: no data 2026-10-09: no data 2026-10-10: no data 2026-10-11: no data 2026-10-12: no data 2026-10-13: no data 2026-10-14: no data 2026-10-15: no data 2026-10-16: no data 2026-10-17: no data 2026-10-18: no data 2026-10-19: no data 2026-10-20: no data 2026-10-21: no data 2026-10-22: no data 2026-10-23: no data 2026-10-24: no data 2026-10-25: no data 2026-10-26: no data 2026-10-27: no data 2026-10-28: no data 2026-10-29: no data 2026-10-30: no data 2026-10-31: no data 2026-11-01: no data 2026-11-02: no data 2026-11-03: no data 2026-11-04: Operational
90 days ago100% uptime over 1 tracked dayToday

Each bar is one UTC day, coloured by the worst state we saw on the official status page.

Recent E2B incidents

  • Intermittent template build errors on US-West-1 · 29 Oct 2026, 09:59 UTC · 1 h 21 min · minor

    resolved · 29 Oct 2026, 11:19 UTC

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

    investigating · 29 Oct 2026, 09:58 UTC

    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.

    Read on status.e2b.dev

  • Degraded performance for sandbox operations on US-West-1 · 27 Oct 2026, 11:27 UTC · minor

    resolved · 27 Oct 2026, 10:57 UTC

    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 · 27 Oct 2026, 10:54 UTC

    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.

    Read on status.e2b.dev

  • Template builds failing · 21 Oct 2026, 14:40 UTC · critical

    resolved · 21 Oct 2026, 14:06 UTC

    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 · 21 Oct 2026, 14:03 UTC

    We have identified an issue causing new template builds to fail.

    Read on status.e2b.dev

  • Increased errors on sandbox pause. · 2 Oct 2026, 19:34 UTC · 24 min · major

    resolved · 2 Oct 2026, 19:58 UTC

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

    identified · 2 Oct 2026, 19:52 UTC

    We’ve identified the issue and are scaling up capacity to mitigate. 

    investigating · 2 Oct 2026, 19:07 UTC

    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.

    Read on status.e2b.dev

  • Elevated error rates when creating sandboxes from snapshots · 15 Sept 2026, 16:53 UTC · 4 h 45 min · major

    resolved · 15 Sept 2026, 21:38 UTC

    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 · 15 Sept 2026, 21:01 UTC

    We’ve deployed the fix, and sandbox creation from snapshots is operating normally. We’re continuing to monitor to confirm stability.

    identified · 15 Sept 2026, 20:06 UTC

    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 · 15 Sept 2026, 17:44 UTC

    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 · 15 Sept 2026, 16:53 UTC

    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.

    Read on status.e2b.dev

  • Elevated errors levels on US cluster from internal migration · 4 Sept 2026, 19:16 UTC · major

    resolved · 4 Sept 2026, 18:46 UTC

    All operations are fully recovered.

    identified · 4 Sept 2026, 18:26 UTC

    During an internal migration operation, a subset of traffic on our US cluster started erroring. Impact peaked at ~15% error rate.

    Read on status.e2b.dev

  • Elevated error rates and slower sandbox start times · 3 Sept 2026, 01:21 UTC · 1 h 41 min · major

    resolved · 3 Sept 2026, 03:02 UTC

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

    monitoring · 3 Sept 2026, 02:32 UTC

    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 · 3 Sept 2026, 02:23 UTC

    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 · 3 Sept 2026, 01:54 UTC

    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 · 3 Sept 2026, 01:44 UTC

    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 · 3 Sept 2026, 01:14 UTC

    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.

    Read on status.e2b.dev

  • Elevated error rates and slower sandbox start times · 3 Sept 2026, 00:02 UTC · 15 min · minor

    resolved · 3 Sept 2026, 00:18 UTC

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

    identified · 3 Sept 2026, 00:14 UTC

    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 · 2 Sept 2026, 23:55 UTC

    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.

    Read on status.e2b.dev

  • Elevated template build failures · 1 Sept 2026, 18:37 UTC · 3 h 1 min · minor

    resolved · 1 Sept 2026, 21:38 UTC

    The build failures have been resolved.

    investigating · 1 Sept 2026, 18:42 UTC

    We are investigating an elevated rate of template build failures. Some builds may fail or run slowly while we work on it.

    investigating · 1 Sept 2026, 18:37 UTC

    We are investigating an elevated rate of template build failures. Some builds may fail or run slowly while we work on it.

    Read on status.e2b.dev

  • Intermittent template build failures · 1 Sept 2026, 13:05 UTC · minor

    resolved · 1 Sept 2026, 01:07 UTC

    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 · 31 Aug 2026, 22:41 UTC

    We corrected the configuration and restored the affected build infrastructure. We are monitoring template-build error rates as the service recovers.

    identified · 31 Aug 2026, 22:37 UTC

    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 · 31 Aug 2026, 21:37 UTC

    We are investigating intermittent failures affecting some template builds. Failed builds may return an internal error. Retrying may succeed.

    Read on status.e2b.dev

  • Increased error rate for pause/resume operations on US cluster · 27 Aug 2026, 14:50 UTC · 2 h 21 min · minor

    resolved · 27 Aug 2026, 17:11 UTC

    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 · 27 Aug 2026, 16:17 UTC

    We have deployed a fix, and the error rates should be returning to normal. We will continue to monitor the situation.

    investigating · 27 Aug 2026, 14:50 UTC

    We are investigating an increased error rate for pause/resume operations. We will post updates as we learn more.

    Read on status.e2b.dev

  • Increased error rate when connecting to paused sandboxes · 25 Aug 2026, 14:00 UTC · minor

    resolved · 25 Aug 2026, 12:32 UTC

    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 · 25 Aug 2026, 11:33 UTC

    We are investigating an increased error rate when connecting to paused sandboxes. Running sandboxes are not affected.

    Read on status.e2b.dev

  • EU region sandbox traffic connection issues · 21 Aug 2026, 23:17 UTC · 9 min · major

    resolved · 21 Aug 2026, 23:26 UTC

    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 · 21 Aug 2026, 23:18 UTC

    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 · 21 Aug 2026, 23:03 UTC

    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.

    Read on status.e2b.dev

  • Elevated error rates for sandbox operations · 20 Aug 2026, 16:25 UTC · 4 h 3 min · minor

    resolved · 20 Aug 2026, 20:27 UTC

    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 · 20 Aug 2026, 18:41 UTC

    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 · 20 Aug 2026, 18:02 UTC

    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 · 20 Aug 2026, 17:51 UTC

    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 · 20 Aug 2026, 17:23 UTC

    Service is recovering. Sandbox operations are stabilizing and error rates are returning to normal. We continue to monitor closely.

    investigating · 20 Aug 2026, 17:15 UTC

    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 · 20 Aug 2026, 16:25 UTC

    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.

    Read on status.e2b.dev

E2B is listed under Dev tools. Status data comes from the official status page and is checked every 5 minutes.All AI service statuses

Updated