Is Bunny.net Down?

No — Bunny.net is up

Reachable from all 8 checked regions

Average response time: 30ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://status.bunny.net

Bunny.net uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

48ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

26-day clean streak

Aug 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

bom

26ms

DNS 0ms TCP 1ms TLS 5ms TTFB 9ms

cdg

40ms

DNS 0ms TCP 1ms TLS 11ms TTFB 19ms

dfw

22ms

DNS 0ms TCP 0ms TLS 4ms TTFB 9ms

ewr

31ms

DNS 0ms TCP 1ms TLS 10ms TTFB 19ms

fra

26ms

DNS 0ms TCP 1ms TLS 4ms TTFB 9ms

gru

27ms

DNS 0ms TCP 1ms TLS 7ms TTFB 12ms

iad

26ms

DNS 0ms TCP 1ms TLS 4ms TTFB 9ms

jnb

45ms

DNS 0ms TCP 0ms TLS 16ms TTFB 20ms

What Bunny.net does

Bunny.net is a content delivery network that also sells the pieces around it: Edge Storage for origin files, DNS, a video Stream product with transcoding and live streaming, an image Optimizer, Origin Shield, Edge Scripting and the Bunny Fonts service. Sites route their static assets and video through it, so a Bunny outage surfaces on customer sites rather than on Bunny's own domain.

What an outage looks like

Images, stylesheets and scripts fail to load on sites that route assets through the CDN, leaving pages rendered without styling. Video players stall or refuse to start when Stream or its transcoding service is affected. DNS resolution fails for zones hosted on Bunny DNS, which takes down the whole site rather than only its assets. Dashboard logins and API calls from deployment pipelines fail separately.

What to do about it

Check status.bunny.net, which lists CDN, DNS, Edge Storage, Stream, Live Stream, Optimizer, Origin Shield, Edge Scripting, Bunny Shield, Bunny Database, Bunny Fonts and CDN Logging as separate components with 90-day uptime for each. Identify which one your site actually depends on before assuming a full outage. If DNS is the affected component the impact is far wider than a CDN fault, because nothing resolves.

Is it down for everyone, or just you?

If this page says Bunny.net is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Bunny.net outage FAQ

Is bunny.net down or is it my origin server?

Compare the per-region measurements on this page with status.bunny.net. A CDN serves cached content from edge nodes, so an origin that is down often shows as stale-but-working assets rather than errors, while a CDN fault shows as assets failing across many regions at once. If one of our regions fails and others pass, that points at a single edge location rather than the platform.

Does a bunny.net CDN outage take my whole site down?

Usually not the whole site. If only the CDN is affected, HTML served from your own origin still loads while images, CSS and JavaScript routed through Bunny fail, which renders as an unstyled page. The exception is Bunny DNS: if your zone is hosted there and DNS is the failing component, nothing resolves and the site is fully unreachable regardless of where the rest is served from.

Does an outage affect video already uploaded to Bunny Stream?

Stored video is not lost. Bunny tracks Stream, its transcoding service and Live Stream as three separate components, so playback of existing files can fail while uploads succeed, or transcoding can back up while finished videos still play. A transcoding outage typically delays newly uploaded video becoming playable rather than affecting anything already processed.

Should I fail over to my origin during a CDN outage?

Only if your origin can take the traffic. Pointing DNS straight at an origin sized for cached traffic is a common way to turn a partial outage into a full one. Bunny's Origin Shield exists to keep origin load low, and it is a separate status component, so check whether it is the failing piece before making a routing change under load.

How we measure this

We request Bunny.net's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Bunny.net publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Bunny.net goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required