Is E2B down? › Outage history › Jul 1, 2026
E2B partial outage on Jul 1, 2026: what happened
On Jul 1, 2026, the E2B status page reported "EU cluster degradation". About 3 hours 29 min: from Jul 1, 2026, 15:16 UTC to Jul 1, 2026, 18:45 UTC, by the official start and resolution times.
E2B right now
At our last refresh (Oct 22, 2026, 12:35 UTC) E2B was up: All Systems Operational.
- Started
- Jul 1, 2026, 15:16 UTC
- Resolved
- Jul 1, 2026, 18:45 UTC
- Duration
- 3 hours 29 min
- Official impact
- Major
- Source
- EU cluster degradation on the E2B status page
The E2B status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
What caused the E2B partial outage?
The E2B status page has not published a cause. When it identified the problem at 15:36 UTC on Jul 1, 2026, it said: "We've identified the root cause and are rolling out a fix. Service should begin returning to normal shortly."
When was it fixed?
The E2B status page marked it resolved at Jul 1, 2026, 18:45 UTC, 3 hours 29 min after it started. A fix was in place and being monitored from Jul 1, 2026, 15:44 UTC. Its resolution note: "The issue has been resolved, and all services are operating normally."
Timeline of official updates
Every update the E2B status page posted, oldest first. Times are UTC.
Jul 1, 2026, 15:16 UTC investigating
We are investigating an issue causing errors on our EU cluster. We will share updates as we learn more. We apologize for the inconvenience.
Jul 1, 2026, 15:23 UTC investigating
This incident is affecting sandbox API operations and template builds. We are still investigating the root cause.
Jul 1, 2026, 15:36 UTC identified
We've identified the root cause and are rolling out a fix. Service should begin returning to normal shortly.
Jul 1, 2026, 15:44 UTC monitoring
The fix has been fully deployed, and service has returned to normal. We are continuing to monitor the system closely to ensure everything remains stable. We sincerely apologize for the disruption and appreciate your patience while we worked to resolve the issue.
Jul 1, 2026, 18:45 UTC resolved
The issue has been resolved, and all services are operating normally.
E2B partial outage questions
What caused the E2B partial outage on Jul 1, 2026?
The E2B status page has not published a cause. When it identified the problem (Jul 1, 2026, 15:36 UTC) it said: "We've identified the root cause and are rolling out a fix. Service should begin returning to normal shortly."
When was the E2B partial outage on Jul 1, 2026 fixed?
The E2B status page marked it resolved at Jul 1, 2026, 18:45 UTC, 3 hours 29 min after it started. A fix was in place and being monitored from Jul 1, 2026, 15:44 UTC. Its resolution note: "The issue has been resolved, and all services are operating normally."
How long did the E2B partial outage last?
About 3 hours 29 min: from Jul 1, 2026, 15:16 UTC to Jul 1, 2026, 18:45 UTC, by the official start and resolution times.
Was E2B completely down?
No. The E2B status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
Other recent E2B incidents
- Template builds failing Oct 21, 2026, 14:40 UTC, duration not stated
- Increased errors on sandbox pause. Oct 2, 2026, 19:34 UTC, 24 minutes
- Elevated error rates when creating sandboxes from snapshots Sep 15, 2026, 16:53 UTC, 4 hours 45 min
- Elevated errors levels on US cluster from internal migration Sep 4, 2026, 19:16 UTC, duration not stated
- Elevated error rates and slower sandbox start times Sep 3, 2026, 01:21 UTC, 1 hour 41 min
- Elevated error rates and slower sandbox start times Sep 3, 2026, 00:02 UTC, 15 minutes
Full E2B outage history and biggest outages → · Recent outages across all services →
Quotes are the E2B status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with E2B. Times are UTC.