Skip to content

Outage tracker / Bunny CDN

Is Bunny CDN down?

I'm having a problem

Vendor reports no incidentWhat Bunny CDN reports

Bunny CDN reports no incident on its status page.

As of the last successful poll, 2026-10-23 23:13 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 2 minutes ago

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

As of Oct 23, 2026, 11:21 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 Oct 23, 2026, 11:21 PM UTC
US-East971 msChecks passing
US-West1869 msChecks passing
Europe605 msChecks passing
Asia-Pacific1279 msChecks passing
US-Central288 msChecks passing
Canada311 msChecks passing
UK156 msChecks passing
Southeast Asia834 msChecks passing
Australia1111 msChecks passing
South America7643 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 Oct 23, 2026, 10:57 PM UTC
Bunny CDN's own status page shows no incident, and our checks of Bunny CDN pass 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
1.4sp95 · 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-09-24 UTC: p95 599ms2026-09-25 UTC: p95 599ms2026-09-26 UTC: p95 434ms2026-09-27 UTC: p95 442ms2026-09-28 UTC: p95 513ms2026-09-29 UTC: p95 442ms2026-09-30 UTC: p95 461ms2026-10-01 UTC: p95 575ms2026-10-02 UTC: p95 478ms2026-10-03 UTC: p95 458ms2026-10-04 UTC: p95 495ms2026-10-05 UTC: p95 458ms2026-10-06 UTC: p95 503ms2026-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.4s
Sep 24Oct 8Oct 23
US-West
1.2sp95 · 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-09-24 UTC: p95 798ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 876ms2026-09-27 UTC: p95 850ms2026-09-28 UTC: p95 851ms2026-09-29 UTC: p95 735ms2026-09-30 UTC: p95 711ms2026-10-01 UTC: p95 676ms2026-10-02 UTC: p95 642ms2026-10-03 UTC: p95 653ms2026-10-04 UTC: p95 695ms2026-10-05 UTC: p95 718ms2026-10-06 UTC: p95 623ms2026-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.2s
Sep 24Oct 8Oct 23
Europe
663msp95 · 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-09-24 UTC: p95 332ms2026-09-25 UTC: p95 400ms2026-09-26 UTC: p95 386ms2026-09-27 UTC: p95 213ms2026-09-28 UTC: p95 250ms2026-09-29 UTC: p95 452ms2026-09-30 UTC: p95 599ms2026-10-01 UTC: p95 313ms2026-10-02 UTC: p95 243ms2026-10-03 UTC: p95 250ms2026-10-04 UTC: p95 243ms2026-10-05 UTC: p95 227ms2026-10-06 UTC: p95 418ms2026-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 663ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.2sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 909ms2026-09-27 UTC: p95 919ms2026-09-28 UTC: p95 996ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 895ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 891ms2026-10-03 UTC: p95 910ms2026-10-04 UTC: p95 950ms2026-10-05 UTC: p95 934ms2026-10-06 UTC: p95 934ms2026-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.2s
Sep 24Oct 8Oct 23
US-Central
591msp95 · 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-24 UTC: p95 408ms2026-09-25 UTC: p95 537ms2026-09-26 UTC: p95 675ms2026-09-27 UTC: p95 580ms2026-09-28 UTC: p95 731ms2026-09-29 UTC: p95 633ms2026-09-30 UTC: p95 629ms2026-10-01 UTC: p95 529ms2026-10-02 UTC: p95 520ms2026-10-03 UTC: p95 475ms2026-10-04 UTC: p95 522ms2026-10-05 UTC: p95 536ms2026-10-06 UTC: p95 612ms2026-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 591ms
Sep 24Oct 8Oct 23
Canada
1.4sp95 · 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-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 669ms2026-09-26 UTC: p95 347ms2026-09-27 UTC: p95 473ms2026-09-28 UTC: p95 498ms2026-09-29 UTC: p95 410ms2026-09-30 UTC: p95 384ms2026-10-01 UTC: p95 412ms2026-10-02 UTC: p95 505ms2026-10-03 UTC: p95 451ms2026-10-04 UTC: p95 306ms2026-10-05 UTC: p95 304ms2026-10-06 UTC: p95 276ms2026-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.4s
Sep 24Oct 8Oct 23
UK
537msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 230ms2026-09-25 UTC: p95 271ms2026-09-26 UTC: p95 485ms2026-09-27 UTC: p95 522ms2026-09-28 UTC: p95 449ms2026-09-29 UTC: p95 376ms2026-09-30 UTC: p95 420ms2026-10-01 UTC: p95 378ms2026-10-02 UTC: p95 332ms2026-10-03 UTC: p95 317ms2026-10-04 UTC: p95 292ms2026-10-05 UTC: p95 238ms2026-10-06 UTC: p95 154ms2026-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 537ms
Sep 24Oct 8Oct 23
Southeast Asia
2.5sp95 · 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-09-24 UTC: p95 749ms2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.1s2026-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.5s
Sep 24Oct 8Oct 23
Australia
1.6sp95 · 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-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 804ms2026-09-27 UTC: p95 800ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 845ms2026-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.6s
Sep 24Oct 8Oct 23
South America
8.6sp95 · 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-09-24 UTC: p95 621ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 876ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 792ms2026-10-01 UTC: p95 938ms2026-10-02 UTC: p95 915ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 895ms2026-10-05 UTC: p95 2.4s2026-10-06 UTC: p95 3.8s2026-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 8.6s
Sep 24Oct 8Oct 23

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: Checks passingUS-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

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: 971msstatus code: 200checked: Oct 23, 2026, 11:15 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: 1869msstatus code: 200checked: Oct 23, 2026, 11:17 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: 288msstatus code: 200checked: Oct 23, 2026, 11:09 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: 311msstatus code: 200checked: Oct 23, 2026, 11:19 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: 7643msstatus code: 200checked: Oct 23, 2026, 11:12 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: 605msstatus code: 200checked: Oct 23, 2026, 11:21 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: 156msstatus code: 200checked: Oct 23, 2026, 11:04 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: 1279msstatus code: 200checked: Oct 23, 2026, 11:21 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: 834msstatus code: 200checked: Oct 23, 2026, 11:21 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: 1111msstatus code: 200checked: Oct 23, 2026, 11:21 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

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
CDN Synchronization Delays, 3h 19mdeclared on their status page2026-09-21
Increased encoding processing time, 84h 46mdeclared on their status page2026-09-17

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

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>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.bunny.net/region
secondary
https://bunny.net/
secondary
https://bunnycdn.statuspage.io/api/v2/status.json

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.