ChangesE2BVolumes content inaccessible outside of sandbox
E2B: Major incident: Volumes content inaccessible outside of sandbox
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what E2B removed; blue is what they added. Muted text is unchanged context.
Before: not present
After: Volumes content inaccessible outside of sandbox
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-05 00:08 UTC
Before: not present
After: 2026-08-05 00:17 UTC
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
Wednesday, August 5
1 incident change
- MajorMajor incident
Volumes content inaccessible outside of sandboxthis change