E2B reported "Increased errors on sandbox pause." on its status page at 2026-10-02 19:34 UTC.

E2B did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-02 19:34 UTC and ended at 2026-10-02 19:58 UTC. It lasted 24 min.

How do I get alerts for E2B?

Subscribe to the E2B live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of E2B. outages.live reads it every few minutes and keeps every update.

E2BIncident · 2026-10-02 19:34 UTC

Increased errors on sandbox pause.

ResolvedOfficial update

This incident has been resolved. Sandbox pause and resume are working normally.

The latest update from E2B.

State

Resolved

Started

29 d ago

2026-10-02 19:34 UTC

Lasted

24 min

until 2026-10-02 19:58 UTC

Worst impact

Partial outage

Timeline

3 updates

19:3419:4019:4619:5219:58

Partial outageUpdate postedTimes in UTC

Investigating

18 min 75%

Identified

6 min 25%

Updates

Times in UTC

As posted by E2B

Resolved2026-10-02 19:58 UTC

This incident has been resolved. Sandbox pause and resume are working normally.

Identified2026-10-02 19:52 UTC

We’ve identified the issue and are scaling up capacity to mitigate.

Investigating2026-10-02 19:07 UTC

We’re seeing increased errors on sandbox pause and resume and are investigating. We’re investigating the root cause and will post an update as soon as we know more.

E2B in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 41 min

This incident

77% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 45 min

median 1 h 41 min

90 days agoToday

Other E2B incidents

All incidents

E2B·Intermittent template build errors on US-West-1

The issue has been fully resolved. We apologize for the disruption. If you are still seeing issues, please let us know.

Resolvedresolved 3 d ago

E2B·Elevated error rates when creating sandboxes from snapshots

This incident has been fully resolved. We’ll publish a postmortem soon with more details on the cause and resolution. We apologize again for the disruption.

Resolvedresolved 46 d ago

E2B·Elevated error rates and slower sandbox start times

This incident has been resolved. Sandbox creation and API error rates are back to normal. We apologize for the disruption.

Resolvedresolved 59 d ago

E2B·Elevated error rates and slower sandbox start times

Sandbox start times and error rates have returned to normal and the incident is fully resolved.

Resolvedresolved 59 d ago

E2B·Elevated template build failures

The build failures have been resolved.

Resolvedresolved 60 d ago

Follow E2B

Your coding agent knows when E2B is down, and tells you when a failure is theirs, not yours. You can also get E2B incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "e2b" and tell me if E2B has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=e2b

Slack

/feed subscribe https://outages.cc/feed.xml?providers=e2b

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane