E2B

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-21 14:03 UTC

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

2. resolved 2026-10-21 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...

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 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.

2. identified 2026-10-02 19:52 UTC

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

3. resolved 2026-10-02 19:58 UTC

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

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 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.

2. identified 2026-09-15 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.

3. identified 2026-09-15 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.

4. monitoring 2026-09-15 21:01 UTC

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

5. resolved 2026-09-15 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.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-04 18:26 UTC

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

2. resolved 2026-09-04 18:46 UTC

   All operations are fully recovered.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-03 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.

2. identified 2026-09-03 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.

3. identified 2026-09-03 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...

4. identified 2026-09-03 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.

5. monitoring 2026-09-03 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.

6. resolved 2026-09-03 03:02 UTC

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

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 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.

2. identified 2026-09-03 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.

3. resolved 2026-09-03 00:18 UTC

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

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-01 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.

2. investigating 2026-09-01 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.

3. resolved 2026-09-01 21:38 UTC

   The build failures have been resolved.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-31 21:37 UTC

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

2. identified 2026-08-31 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.

3. monitoring 2026-08-31 22:41 UTC

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

4. resolved 2026-09-01 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.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 14:50 UTC

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

2. monitoring 2026-08-27 16:17 UTC

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

3. resolved 2026-08-27 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.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-25 11:33 UTC

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

2. resolved 2026-08-25 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...

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-21 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.

2. monitoring 2026-08-21 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.

3. resolved 2026-08-21 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.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. investigating 2026-08-20 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.

2. investigating 2026-08-20 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

3. monitoring 2026-08-20 17:23 UTC

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

4. monitoring 2026-08-20 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

5. monitoring 2026-08-20 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.

6. monitoring 2026-08-20 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...

7. resolved 2026-08-20 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.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-05 00:08 UTC

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

2. resolved 2026-08-05 00:17 UTC

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

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-04 15:31 UTC

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

2. resolved 2026-08-04 17:15 UTC

   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

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-24 16:50 UTC

   Monitoring cluster recovery from exhaustion

2. resolved 2026-07-24 17:07 UTC

   Cluster capacity is sufficient, and we are continuing monitoring the situation.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-24 06:52 UTC

   Stripe backend looks degrading, we are investigating affected components.

2. resolved 2026-07-24 08:48 UTC

   We identified and recovered affected data. No customer operation impacted.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 13:35 UTC

   Degraded performance for sandbox pause operation.

2. monitoring 2026-07-23 13:44 UTC

   Core issue identified and fixed. Monitoring systems recovery.

3. resolved 2026-07-23 17:09 UTC

   Resolved this

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-22 05:40 UTC

   Investigating this

2. identified 2026-07-22 06:30 UTC

   We identified and resolved issue, now traffic should be recovering.

3. monitoring 2026-07-22 06:50 UTC

   Monitoring system recovery

4. resolved 2026-07-22 08:14 UTC

   Resolved this

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-16 08:55 UTC

   Dashboard auth isn't down

2. monitoring 2026-07-16 09:11 UTC

   The issue seems to be resolved

3. resolved 2026-07-16 09:17 UTC

   Issue confirmed by our auth provider, waiting for root cause. A configuration update caused some legitimate authentication-related requests to be incorrectly blocked.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-01 15:16 UTC

   We are investigating an issue causing errors on our EU cluster. We will share updates as we learn more. We apologize for the inconvenience.

2. investigating 2026-07-01 15:23 UTC

   This incident is affecting sandbox API operations and template builds. We are still investigating the root cause.

3. identified 2026-07-01 15:36 UTC

   We've identified the root cause and are rolling out a fix. Service should begin returning to normal shortly.

4. monitoring 2026-07-01 15:44 UTC

   The fix has been fully deployed, and service has returned to normal. We are continuing to monitor the system closely to ensure everything remains stable. We sincerely apologize for the disruption and appreciate your patience while we worked to resolve the issue.

5. resolved 2026-07-01 18:45 UTC

   The issue has been resolved, and all services are operating normally.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-29 10:16 UTC

   We've identified an issue causing an elevated error rate on our EU cluster. The team is working on resolving the situation as soon as possible. We sincerely apologize for the inconvenience.

2. resolved 2026-06-29 10:27 UTC

   The situation has been fully resolved, and the EU cluster is fully operational again. We apologize again for the inconvenience.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 03:33 UTC

   We're currently observing elevated 503 errors impacting the US cluster. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible.

2. investigating 2026-06-25 03:36 UTC

   Sandbox create in US Region is impacted

3. monitoring 2026-06-25 03:37 UTC

   Reverted a recent production change on API side. Monitoring recovery. Dashboard is still currently unavailable.

4. monitoring 2026-06-25 03:48 UTC

   Full revert of production change is complete. Service is fully operational.

5. resolved 2026-06-25 03:52 UTC

   Production components are fully available.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-15 17:23 UTC

   We are investigating an issue affecting sign-up and login to our dashboard. Users may be unable to create accounts or log in. We'll share an update as soon as we have more information.

2. resolved 2026-06-15 18:23 UTC

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

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-02 22:56 UTC

   We’re investigating intermittent timeouts affecting volume requests.

2. investigating 2026-06-03 16:51 UTC

   We continue to investigate intermittent volume request failures affecting persistent volumes. Our investigation has identified instability in the underlying NFS storage layer as the likely source of the issue. We are seeing elevated timeout, retransmission, and connection reset...

3. monitoring 2026-06-18 01:32 UTC

   We've improved the underlying storage infrastructure, and are monitoring to ensure that the performance has returned to normal.

4. resolved 2026-06-23 06:13 UTC

   The infrastructure improvements have resolved the issue.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-02 16:23 UTC

   We're seeing degraded performance impacting sandbox starts and resumes. The team is working on resolving the issue as soon as possible. We apologize for the inconvenience.

2. identified 2026-06-02 18:31 UTC

   We have exhausted the available capacity in our US cluster and are currently moving workloads onto additional compute capacity to restore normal service. Service should gradually improve as these changes take effect.

3. monitoring 2026-06-02 18:39 UTC

   The US cluster has been restored to normal operation. We are continuing to monitor the situation closely to ensure services remain stable. If you continue to experience any issues, please contact our support team.

4. resolved 2026-06-02 20:11 UTC

   The situation has been resolved. Please reach out if you encounter any errors going forward.

Excerpts are shortened. Read the full incident on E2B's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 10:56 UTC

   We're seeing degraded performance impacting sandbox starts and resumes. We're investigating the issue

2. monitoring 2026-06-02 13:13 UTC

   The issue has been resolved, and the cluster is fully operational again. We are monitoring the situation closely. We apologize for any issues this may have caused.

3. resolved 2026-06-02 14:32 UTC

   The issue has been resolved, and the cluster is fully operational again. Please let us know if you continue to experience any issues.

Excerpts are shortened. Read the full incident on E2B's status page.