Skip to content

Outage tracker / Bunny CDN

Is Bunny CDN down?

I'm having a problem

Vendor lists an old incident, not shown as liveWhat Bunny CDN reports

Bunny CDN still lists an incident opened on 2026-10-28, last updated 2026-11-04; it has been open past 72 hours, so we do not show it as live.

As of the last successful poll, 2026-11-05 15:01 UTC.

Bunny CDN's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 3 minutes ago

Our checks of Bunny CDN pass from all 10 regions we check.

As of Nov 5, 2026, 3:04 PM UTC, RealUptime's checks of Bunny CDN passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:04 PM UTC
US-East731 msChecks passing
US-West1186 msChecks passing
Europe537 msChecks passing
Asia-Pacific1834 msChecks passing
US-Central851 msChecks passing
Canada355 msChecks passing
UK178 msChecks passing
Southeast Asia1419 msChecks passing
Australia410 msChecks passing
South America932 msChecks passing
their status pagetheir claim, not our reading

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

from Bunny CDN's own status page, checked Nov 5, 2026, 2:27 PM UTC

Bunny CDN reports an active incident: Security update regarding one of our infrastructure providers (all systems operational, since Oct 28, 2026, 11:40 AM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.

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
1.1sp95 · 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-10-07 UTC: p95 562ms2026-10-08 UTC: p95 618ms2026-10-09 UTC: p95 565ms2026-10-10 UTC: p95 509ms2026-10-11 UTC: p95 534ms2026-10-12 UTC: p95 441ms2026-10-13 UTC: p95 529ms2026-10-14 UTC: p95 551ms2026-10-15 UTC: p95 440ms2026-10-16 UTC: p95 554ms2026-10-17 UTC: p95 894ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 861ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 998ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-West
1.8sp95 · 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-10-07 UTC: p95 593ms2026-10-08 UTC: p95 512ms2026-10-09 UTC: p95 593ms2026-10-10 UTC: p95 746ms2026-10-11 UTC: p95 685ms2026-10-12 UTC: p95 721ms2026-10-13 UTC: p95 681ms2026-10-14 UTC: p95 693ms2026-10-15 UTC: p95 630ms2026-10-16 UTC: p95 650ms2026-10-17 UTC: p95 953ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 628ms2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Europe
1.0sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 533ms2026-10-08 UTC: p95 249ms2026-10-09 UTC: p95 277ms2026-10-10 UTC: p95 248ms2026-10-11 UTC: p95 248ms2026-10-12 UTC: p95 349ms2026-10-13 UTC: p95 282ms2026-10-14 UTC: p95 201ms2026-10-15 UTC: p95 191ms2026-10-16 UTC: p95 306ms2026-10-17 UTC: p95 431ms2026-10-18 UTC: p95 522ms2026-10-19 UTC: p95 793ms2026-10-20 UTC: p95 542ms2026-10-21 UTC: p95 407ms2026-10-22 UTC: p95 537ms2026-10-23 UTC: p95 660ms2026-10-24 UTC: p95 714ms2026-10-25 UTC: p95 390ms2026-10-26 UTC: p95 410ms2026-10-27 UTC: p95 416ms2026-10-28 UTC: p95 617ms2026-10-29 UTC: p95 535ms2026-10-30 UTC: p95 575ms2026-10-31 UTC: p95 599ms2026-11-01 UTC: p95 577ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 908ms2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Asia-Pacific
2.5sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 955ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 966ms2026-10-11 UTC: p95 963ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 803ms2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 3.4s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
US-Central
1.2sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 425ms2026-10-08 UTC: p95 440ms2026-10-09 UTC: p95 426ms2026-10-10 UTC: p95 368ms2026-10-11 UTC: p95 395ms2026-10-12 UTC: p95 483ms2026-10-13 UTC: p95 479ms2026-10-14 UTC: p95 649ms2026-10-15 UTC: p95 559ms2026-10-16 UTC: p95 722ms2026-10-17 UTC: p95 822ms2026-10-18 UTC: p95 908ms2026-10-19 UTC: p95 950ms2026-10-20 UTC: p95 919ms2026-10-21 UTC: p95 669ms2026-10-22 UTC: p95 492ms2026-10-23 UTC: p95 590ms2026-10-24 UTC: p95 944ms2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 728ms2026-10-29 UTC: p95 818ms2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Canada
627msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 483ms2026-10-08 UTC: p95 570ms2026-10-09 UTC: p95 403ms2026-10-10 UTC: p95 432ms2026-10-11 UTC: p95 430ms2026-10-12 UTC: p95 424ms2026-10-13 UTC: p95 428ms2026-10-14 UTC: p95 407ms2026-10-15 UTC: p95 474ms2026-10-16 UTC: p95 494ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 473ms2026-10-26 UTC: p95 406ms2026-10-27 UTC: p95 522ms2026-10-28 UTC: p95 312ms2026-10-29 UTC: p95 745ms2026-10-30 UTC: p95 658ms2026-10-31 UTC: p95 617ms2026-11-01 UTC: p95 616ms2026-11-02 UTC: p95 714ms2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 766ms2026-11-05 UTC: p95 627ms
Oct 7Oct 21Nov 5
UK
773msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 172ms2026-10-08 UTC: p95 196ms2026-10-09 UTC: p95 249ms2026-10-10 UTC: p95 286ms2026-10-11 UTC: p95 316ms2026-10-12 UTC: p95 363ms2026-10-13 UTC: p95 330ms2026-10-14 UTC: p95 270ms2026-10-15 UTC: p95 250ms2026-10-16 UTC: p95 312ms2026-10-17 UTC: p95 452ms2026-10-18 UTC: p95 602ms2026-10-19 UTC: p95 730ms2026-10-20 UTC: p95 854ms2026-10-21 UTC: p95 710ms2026-10-22 UTC: p95 609ms2026-10-23 UTC: p95 534ms2026-10-24 UTC: p95 512ms2026-10-25 UTC: p95 304ms2026-10-26 UTC: p95 257ms2026-10-27 UTC: p95 187ms2026-10-28 UTC: p95 546ms2026-10-29 UTC: p95 698ms2026-10-30 UTC: p95 644ms2026-10-31 UTC: p95 750ms2026-11-01 UTC: p95 484ms2026-11-02 UTC: p95 755ms2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 773ms
Oct 7Oct 21Nov 5
Southeast Asia
2.2sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 911ms2026-10-10 UTC: p95 985ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 976ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.6s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
Australia
2.1sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 957ms2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 995ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 842ms2026-10-29 UTC: p95 911ms2026-10-30 UTC: p95 831ms2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 975ms2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
South America
2.0sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.8s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 944ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 9.4s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 923ms2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 2.9s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Why some readings show as awaiting data. 1 of 20 readings for Bunny CDN came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Bunny CDN's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Bunny CDN

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Awaiting dataUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DashboardUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DocumentationUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • FontsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • StorageUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Bunny CDN reports an incident on its status page, and again when it reports it resolved.

Get an email when Bunny CDN reports an incident

Email me when Bunny CDN reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Bunny CDN's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 731msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
      Checks passinglatency: 1186msstatus code: 200checked: Nov 5, 2026, 2:59 PM 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
      Checks passinglatency: 851msstatus code: 200checked: Nov 5, 2026, 2:51 PM 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
      Checks passinglatency: 355msstatus code: 200checked: Nov 5, 2026, 3:00 PM 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
    Checks passinglatency: 932msstatus code: 200checked: Nov 5, 2026, 3:04 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 537msstatus code: 200checked: Nov 5, 2026, 3:01 PM 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
      Checks passinglatency: 178msstatus code: 200checked: Nov 5, 2026, 2:57 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1834msstatus code: 200checked: Nov 5, 2026, 2:54 PM 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
      Checks passinglatency: 1419msstatus code: 200checked: Nov 5, 2026, 2:50 PM 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
      Checks passinglatency: 410msstatus code: 200checked: Nov 5, 2026, 2:57 PM 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 probe events

Security update regarding one of our infrastructure providersdeclared on their status page2026-10-28
Performance degradation in DE, 1h 58mdeclared on their status page2026-10-24
Storage operations in DE and Stream uploads performance degradation, 13h 10mdeclared on their status page2026-10-15
Network issues in Frankfurt, 10h 31mdeclared on their status page2026-10-15
Database Performance Degradation, 12h 23mdeclared on their status page2026-10-07
CDN Log forwarding performance degradation, 9h 57mdeclared on their status page2026-10-05
Degraded Optimizer Response times, 2h 25mdeclared on their status page2026-09-25
Intermittent Login/API Timeouts in Poland, 30mdeclared on their status page2026-09-22

check 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 check readings and Bunny CDN's own claim at the time, side by side.

Full check history for Bunny CDN: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Bunny CDN uptime by RealUptime's checksLive, from this page's own readings.
[![Bunny CDN uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Bunny CDN down?", https://realuptime.io/outages/bunny-cdn. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.bunny.net/region
secondary
https://bunny.net/
secondary
https://bunnycdn.statuspage.io/api/v2/status.json
secondary
https://storage.bunnycdn.com/
secondary
https://dash.bunny.net/
secondary
https://fonts.bunny.net/css?family=roboto
secondary
https://bunny.net/docs

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.bunny.net

RealUptime is not affiliated with Bunny CDN; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.