E2B: High demand caused resource exhaustion
GitHub outage, Jul 24, 2026 · 9 vendors, 12 incidents
E2B’s incident started in the same window without naming GitHub (timing only, not evidence of a link). (timing only, posted +13 min vs GitHub’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["GitHub<br/>posted 16:17 UTC"]:::root
h1["Within an hour<br/>2 vendors, 2 blamed GitHub<br/>Bolt.new, CircleCI"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed GitHub<br/>Bolt.new"]:::blames
root --> h4
me["E2B (this incident)<br/>posted +13 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Sandbox Pause/Resume/Create
Timeline of updates
- monitoring
Monitoring cluster recovery from exhaustion
- resolved
Cluster capacity is sufficient, and we are continuing monitoring the situation.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 17:03 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
de868032c0365539…
Impact, status and times are the vendor’s own, as last archived. View on status.e2b.dev (opens in new tab).