Increased error rate when connecting to paused sandboxes
Aug 25, 11:33 UTCAug 25, 12:32 UTC
Duration
59m
Impact
Minor
Root cause
Not disclosed
E2B, 90 days
15 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Aug 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 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 · Aug 25, 11:33 UTC
We are investigating an increased error rate when connecting to paused sandboxes. Running sandboxes are not affected.
More from E2B
Full historyElevated 503 errors in EU-West-1lasted 1h 27mIntermittent template build errors on US-West-1lasted 1h 22mDegraded performance for sandbox operations on US-West-1lasted 3mTemplate builds failinglasted 3mIncreased errors on sandbox pause.lasted 51mElevated error rates when creating sandboxes from snapshotslasted 4h 45m