Is Bun down?
Bun is up
Right now
No. Bun Install script answers UpButler's independent probe; no machine-readable official status.
No official machine-readable status
For agents
proceed
Proceed.
GET upbutler.com/status/bun/status.agent.json
MCP: upstream_status {"service":"bun"}
The Bun runtime download and install endpoints. Bun has no status page; UpButler probes the install script.
What UpButler measured
Install script is answeringHTTP 200 · 125 ms
One request without credentials to bun.sh every two minutes, from eu-central (one location, not a global view). An answer shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 06:08 UTC
Bun incidents, last 90 days
Without a machine-readable source there is no incident history to show. Bun keeps its own at bun.sh.
Get alerted when Bun goes down
No account. One email when our probe cannot reach Bun for several minutes, one when it can again. You confirm the address first, and every email has a one-click unsubscribe.
On UpButler? Add Bun as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Bun's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/bun)Tell your outage from Bun's
Declare that your project depends on Bun. When one of your monitors fails while Bun 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.
# upbutler.yaml
dependencies:
- buncurl -s https://upbutler.com/status/bun/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "bun",
"verdict": "proceed",
"status": "operational",
"reason": "Bun Install script answers UpButler's independent probe; no machine-readable official status",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 200
}
}Questions
- Is Bun down right now?
- No. As of 2026-10-10 07:17 UTC, Bun is up. This page reads the status again every 2 minutes.
- Where does this status come from?
- Bun publishes no status page; only the independent probe is shown.
- What does UpButler's own Bun check prove?
- Every two minutes UpButler sends one request without credentials to the Bun Install script (bun.sh) from eu-central. Any answer from the edge, usually HTTP 200, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
- How can my agent or app check Bun status?
- Fetch https://upbutler.com/status/bun/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":"bun"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Bun's?
- Add "bun" to the dependencies of your UpButler workspace. When one of your monitors fails while Bun 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.
Also check
UpButler is not affiliated with Bun. Status and incident text belong to Bun and are read from their public status source; the probe result is UpButler's own measurement.