E2B: Increased error rate for pause/resume operations on US cluster

What to do

Check whether you use E2B in us. 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 2h 21m it lasted.
Anything that failed between 2026-08-27 14:50 UTC and 2026-08-27 17:11 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.

investigatingAug 27, 2026, 2:50 PM UTC
We are investigating an increased error rate for pause/resume operations. We will post updates as we learn more.
provider
monitoringAug 27, 2026, 4:17 PM UTC
We have deployed a fix, and the error rates should be returning to normal. We will continue to monitor the situation.
provider
resolvedAug 27, 2026, 5:11 PM UTC
The issue has been resolved and the service is back to normal. Please reach out to our support if you experience any further issues.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is E2B still down?

No, this incident was resolved 2026-08-27 17:11 UTC. For E2B's live state, see https://down.guide/e2b.

How long did it last?

2h 21m, from 2026-08-27 14:50 UTC to 2026-08-27 17:11 UTC, by the times E2B posted.

What was affected?

E2B named in us.

What caused it?

E2B hasn't published a root cause. If it does, it shows here.

Where does this come from?

E2B's official status page, https://status.e2b.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.