Skip to content

Outage tracker / Bunny CDN

Is Bunny CDN down?

Short linkrlup.io/down/bunny-cdn

I'm having a problem

Operationalchecked moments ago

We reached Bunny CDN from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Bunny CDN (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:08 AM UTC
US-East615 msOperational
US-West300 msOperational
Europe67 msOperational
Asia-Pacific607 msOperational
US-Central387 msOperational
Canada256 msOperational
UK117 msOperational
Southeast Asia1022 msOperational
Australia1209 msOperational
South America583 msOperational
their status pagetheir claim, not our reading

Bunny CDN reports: All systems operational (“All Systems Operational”)

from Bunny CDN's own status page, checked Sep 5, 2026, 1:46 AM UTC
Our probes and Bunny CDN's own status page agree: both show Bunny CDN as reachable right now.

Bunny CDN's own component breakdown, as they publish it

  • Stream ServiceOperational
  • WebsiteOperational
  • DashboardOperational
  • Stream - Transcoding ServiceOperational
  • APIOperational
  • Live StreamOperational
  • CDNOperational
  • DNSOperational
  • Edge StorageOperational
  • OptimizerOperational
  • Origin ShieldOperational
  • Bunny FontsOperational
  • Edge ScriptingOperational
  • Magic ContainersOperational
  • Bunny ShieldOperational
  • Bunny DatabaseOperational
  • CDN LoggingOperational

These are Bunny CDN's components, named and scored by Bunny CDN. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Bunny CDN's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Bunny CDN response time, by region

US-East
652msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 312ms2026-08-23 UTC: p95 621ms2026-08-24 UTC: p95 780ms2026-08-25 UTC: p95 663ms2026-08-26 UTC: p95 582ms2026-08-27 UTC: p95 789ms2026-08-28 UTC: p95 954ms2026-08-29 UTC: p95 677ms2026-08-30 UTC: p95 481ms2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 724ms2026-09-02 UTC: p95 639ms2026-09-03 UTC: p95 729ms2026-09-04 UTC: p95 649ms2026-09-05 UTC: p95 652ms
Aug 7Aug 21Sep 5
US-West
754msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 363ms2026-08-23 UTC: p95 645ms2026-08-24 UTC: p95 747ms2026-08-25 UTC: p95 524ms2026-08-26 UTC: p95 702ms2026-08-27 UTC: p95 983ms2026-08-28 UTC: p95 777ms2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 969ms2026-08-31 UTC: p95 765ms2026-09-01 UTC: p95 729ms2026-09-02 UTC: p95 831ms2026-09-03 UTC: p95 772ms2026-09-04 UTC: p95 771ms2026-09-05 UTC: p95 754ms
Aug 7Aug 21Sep 5
Europe
205msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 269ms2026-08-23 UTC: p95 584ms2026-08-24 UTC: p95 444ms2026-08-25 UTC: p95 356ms2026-08-26 UTC: p95 662ms2026-08-27 UTC: p95 448ms2026-08-28 UTC: p95 367ms2026-08-29 UTC: p95 604ms2026-08-30 UTC: p95 319ms2026-08-31 UTC: p95 547ms2026-09-01 UTC: p95 418ms2026-09-02 UTC: p95 502ms2026-09-03 UTC: p95 479ms2026-09-04 UTC: p95 228ms2026-09-05 UTC: p95 205ms
Aug 7Aug 21Sep 5
Asia-Pacific
871msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 779ms2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 1.2s2026-08-30 UTC: p95 1.4s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.2s2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 871ms
Aug 7Aug 21Sep 5
US-Central
466msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 534ms2026-09-04 UTC: p95 496ms2026-09-05 UTC: p95 466ms
Aug 7Aug 21Sep 5
Canada
285msp95 · latest
500ms250ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 458ms2026-09-04 UTC: p95 321ms2026-09-05 UTC: p95 285ms
Aug 7Aug 21Sep 5
UK
178msp95 · latest
250ms125ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 250ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 245ms2026-09-04 UTC: p95 242ms2026-09-05 UTC: p95 178ms
Aug 7Aug 21Sep 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.2s
Aug 7Aug 21Sep 5
South America
1.1sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.5s2026-09-04 UTC: p95 1.7s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5

Is it Bunny CDN, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Bunny CDN -- it cannot diagnose Bunny CDN's own systems.

What we measured, function by function

Bunny CDN answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 615msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Bunny CDN normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 300msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Bunny CDN normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 387msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Bunny CDN normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 256msstatus code: 200checked: Sep 5, 2026, 2:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Bunny CDN normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 583msstatus code: 200checked: Sep 5, 2026, 2:00 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Bunny CDN normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 67msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Bunny CDN normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 117msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Bunny CDN normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 607msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Bunny CDN normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1022msstatus code: 200checked: Sep 5, 2026, 1:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Bunny CDN normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1209msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Bunny CDN normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Bunny CDN, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Bunny CDN yet, which is not evidence that nothing is wrong.

Recent outages

Video Playback and Encoding Failures on Bunny Stream, 1h 51mdeclared on their status page2026-09-03
Network issues in Los Angeles, 4h 18mdeclared on their status page2026-09-03
Network issues in Los Angeles, 1h 12mdeclared on their status page2026-09-02
Database Controller Outage, 8h 24mdeclared on their status page2026-08-25
Storage API degradation in London, 2h 1mdeclared on their status page2026-08-18
Video Delivery Failures on Basic DRM enabled Libraries, 28mdeclared on their status page2026-07-23
Users are unable to login to dash.bunny.net, 14mdeclared on their status page2026-07-17
Storage API Degradation in Germany, 7mdeclared on their status page2026-07-01

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Bunny CDN since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Bunny CDN covering any window you pick, with our measurements and Bunny CDN's own claim at the time, side by side.

Full availability history for Bunny CDN: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Bunny CDN, and again when they can reach it again. That is our own measurement from ten regions, not Bunny CDN's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Bunny CDN uptime measured by RealUptimeLive, from this page's own readings.
[![Bunny CDN uptime measured by RealUptime](https://realuptime.io/outages/bunny-cdn/badge.svg?days=30)](https://realuptime.io/outages/bunny-cdn)
<a href="https://realuptime.io/outages/bunny-cdn"><img src="https://realuptime.io/outages/bunny-cdn/badge.svg?days=30" alt="Bunny CDN uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Bunny CDN's SLA implies, from our measurement

At or above your target

We measured none of downtime for Bunny CDN over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Bunny CDN's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.bunny.net/region
secondary
https://bunny.net/
secondary
https://bunnycdn.statuspage.io/api/v2/status.json
RealUptime is not affiliated with Bunny CDN; the name identifies what we measured, and nothing here speaks for Bunny CDN's own team. We send a single web request to Bunny CDN from 10 regions on our own schedule and time the response. We do not see inside Bunny CDN's systems, do not use an account or real transaction, and are not the same signal Bunny CDN's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Bunny CDN is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.

Related services

AkamaiAmplitudeAnthropicAuth0AWS (Amazon Web Services)