Where does this status come from?

From E2B's own status page API at https://status.e2b.dev. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are E2B's words.

How can my agent or app check E2B status?

Fetch https://upbutler.com/status/e2b/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"e2b"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or E2B's?

Add "e2b" to the dependencies of your UpButler workspace. When one of your monitors fails while E2B has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is E2B down?

Right now

No. E2B is operational.

No incidents reported.

Read from status.e2b.dev 79 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/e2b/status.agent.json

MCP: upstream_status {"service":"e2b"}

Sandboxes that run agent-written code.

What E2B reports

Operational

Taken as is from E2B's own status page API. Incident titles and component names below are theirs.

Open status.e2b.dev

UpButler's independent probe

There is no keyless endpoint of E2B that says anything useful, so UpButler does not probe it. To check your own E2B account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

E2B components

14 operational

Sandbox Pause/Resume/CreateOperational
Sandbox Network TrafficOperational
Persistent VolumesOperational
Template BuildsOperational
Sandbox Pause/Resume/CreateOperational
Sandbox Network TrafficOperational
Persistent VolumesOperational
Template BuildsOperational
Sandbox Pause/Resume/CreateOperational
Sandbox Network TrafficOperational
Template BuildsOperational
Landing PageOperational
DashboardOperational
DocumentationOperational

E2B incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by E2B.

Started (UTC)	Incident	Impact	Lasted
2026-10-02 19:34	Increased errors on sandbox pause.	major	24 min

Tell your outage from E2B's

Declare that your project depends on E2B. When one of your monitors fails while E2B has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - e2b

Ask before you retry

curl -s https://upbutler.com/status/e2b/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "e2b",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is E2B down right now?: No. As of 2026-10-10 05:11 UTC, E2B is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From E2B's own status page API at https://status.e2b.dev. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are E2B's words.
How can my agent or app check E2B status?: Fetch https://upbutler.com/status/e2b/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"e2b"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or E2B's?: Add "e2b" to the dependencies of your UpButler workspace. When one of your monitors fails while E2B has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in hosting and compute

UpButler is not affiliated with E2B. Status and incident text belong to E2B and are read from their public status source; the probe result is UpButler's own measurement.