Volumes content inaccessible outside of sandbox

What to do

• Check whether your product depends on E2B. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 9m it lasted.

  Anything that failed between 2026-08-05 00:08 UTC and 2026-08-05 00:17 UTC may need a replay.

• Subscribe to E2B's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=e2b works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from E2B 2

1. identifiedAug 5, 2026, 12:08 AM UTC

   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.

   provider

2. resolvedAug 5, 2026, 12:17 AM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.