Where does this status come from?

From bunny.net's own status page API at https://status.bunny.net. 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 bunny.net's words.

How can my agent or app check bunny.net status?

Fetch https://upbutler.com/status/bunny/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":"bunny"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or bunny.net's?

Add "bunny" to the dependencies of your UpButler workspace. When one of your monitors fails while bunny.net 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 bunny.net down?

Right now

No. bunny.net is operational.

No incidents reported.

Read from status.bunny.net 38 s ago · every 120s

For agents

proceed

Proceed.

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

MCP: upstream_status {"service":"bunny"}

CDN, storage, DNS and stream.

What bunny.net reports

Operational

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

Open status.bunny.net

UpButler's independent probe

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

Open at bunny.net

Scheduled API Maintenancescheduled maintenance
Starts 2026-10-14 07:00 UTC · API
We will be conducting necessary API maintenance on October 14th, between 07:00 UTC and 09:00 UTC. Brief slight delays in configuration synchronization are expected during this time

Text written by bunny.net, shown unchanged.

bunny.net components

17 operational

WebsiteOperational
DashboardOperational
APIOperational
CDNOperational
DNSOperational
Edge StorageOperational
OptimizerOperational
Origin ShieldOperational
Bunny FontsOperational
Edge ScriptingOperational
Magic ContainersOperational
Bunny ShieldOperational
Bunny DatabaseOperational
CDN LoggingOperational

Stream

Stream ServiceOperational
Stream - Transcoding ServiceOperational
Live StreamOperational

bunny.net incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-10-07 10:13	Database Performance Degradation	minor	12 h 23 min
2026-10-05 23:02	CDN Log forwarding performance degradation	minor	9 h 57 min

Tell your outage from bunny.net's

Declare that your project depends on bunny.net. When one of your monitors fails while bunny.net 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:
  - bunny

Ask before you retry

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

status.agent.json (live)

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

Questions

Is bunny.net down right now?: No. As of 2026-10-10 05:13 UTC, bunny.net is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From bunny.net's own status page API at https://status.bunny.net. 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 bunny.net's words.
How can my agent or app check bunny.net status?: Fetch https://upbutler.com/status/bunny/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":"bunny"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or bunny.net's?: Add "bunny" to the dependencies of your UpButler workspace. When one of your monitors fails while bunny.net 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 cloud and edge

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