Current answer
E2B experienced a partial incident: Volumes content inaccessible outside of sandbox. Resolved on Aug 5, 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
Persistent Volumes
Incident Timeline
Resolved
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.
We apologize for the disruption this caused. If you continue to experience any issues accessing your volumes, please contact our support team.
Aug 5, 2026 at 12:17 AM UTC
Identified
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 mismatch that was introduced in a recent deployment and is working on a fix. We expect to have this resolved shortly.
We apologize for any disruption this may cause. If you're experiencing issues accessing your volumes, please reach out to our support team and we'll be happy to assist.
Our team identified a domain configuration mismatch that was introduced in a recent deployment and is working on a fix. We expect to have this resolved shortly.
We apologize for any disruption this may cause. If you're experiencing issues accessing your volumes, please reach out to our support team and we'll be happy to assist.
Aug 5, 2026 at 12:08 AM UTC
Was your business affected by this E2B outage?
Follow E2B and route available status alerts to email or a team channel.