Current answer
E2B experienced a minor incident: Increased error rate when connecting to paused sandboxes. Resolved on Aug 25, 2026.
The notice publication date does not establish the outage start. Provider resolved: .
Looking for an update now? Check the current status, or follow E2B for future changes.
Provider notice timeline
Affected Components
Sandbox Pause/Resume/Create
Incident Timeline
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.
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.
Aug 25, 2026 at 12:32 PM UTC
Investigating
We are investigating an increased error rate when connecting to paused sandboxes.
Running sandboxes are not affected.
Running sandboxes are not affected.
Aug 25, 2026 at 11:33 AM UTC
Was your business affected by this E2B outage?
Follow E2B and route available status alerts to email or a team channel.