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.

All operations are fully recovered.

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

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

The build failures have been 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.

The issue has been resolved and the service is back to normal. Please reach out to our support if you experience any further issues.

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.

We apologize for the disruption.

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.

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.

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.

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

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

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

Resolved this

Resolved this

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

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

The situation has been fully resolved, and the EU cluster is fully operational again.

We apologize again for the inconvenience.

Production components are fully available.

The infrastructure improvements have resolved the issue.