Skip to content

Outage tracker / Bunny CDN

Is Bunny CDN down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Bunny CDN from all 10 regions we check.

As of Oct 5, 2026, 9:03 PM UTC, Bunny CDN answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 20 min on Sep 30, 2026 (web surface, from UK).

our independent probeslive · checked Oct 5, 2026, 9:03 PM UTC
US-East202 msOperational
US-West326 msOperational
Europe169 msOperational
Asia-Pacific638 msOperational
US-Central299 msOperational
Canada130 msOperational
UK234 msOperational
Southeast Asia1064 msOperational
Australia1097 msOperational
South America464 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 Oct 5, 2026, 8:58 PM 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
464msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 518ms2026-09-07 UTC: p95 488ms2026-09-08 UTC: p95 436ms2026-09-09 UTC: p95 313ms2026-09-10 UTC: p95 403ms2026-09-11 UTC: p95 443ms2026-09-12 UTC: p95 428ms2026-09-13 UTC: p95 461ms2026-09-14 UTC: p95 422ms2026-09-15 UTC: p95 426ms2026-09-16 UTC: p95 515ms2026-09-17 UTC: p95 716ms2026-09-18 UTC: p95 684ms2026-09-19 UTC: p95 797ms2026-09-20 UTC: p95 826ms2026-09-21 UTC: p95 826ms2026-09-22 UTC: p95 617ms2026-09-23 UTC: p95 659ms2026-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 464ms
Sep 6Sep 20Oct 5
US-West
717msp95 · 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-06 UTC: p95 721ms2026-09-07 UTC: p95 650ms2026-09-08 UTC: p95 622ms2026-09-09 UTC: p95 593ms2026-09-10 UTC: p95 636ms2026-09-11 UTC: p95 794ms2026-09-12 UTC: p95 701ms2026-09-13 UTC: p95 802ms2026-09-14 UTC: p95 918ms2026-09-15 UTC: p95 899ms2026-09-16 UTC: p95 779ms2026-09-17 UTC: p95 844ms2026-09-18 UTC: p95 880ms2026-09-19 UTC: p95 884ms2026-09-20 UTC: p95 872ms2026-09-21 UTC: p95 898ms2026-09-22 UTC: p95 878ms2026-09-23 UTC: p95 865ms2026-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 717ms
Sep 6Sep 20Oct 5
Europe
227msp95 · 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-06 UTC: p95 248ms2026-09-07 UTC: p95 312ms2026-09-08 UTC: p95 400ms2026-09-09 UTC: p95 356ms2026-09-10 UTC: p95 252ms2026-09-11 UTC: p95 278ms2026-09-12 UTC: p95 301ms2026-09-13 UTC: p95 287ms2026-09-14 UTC: p95 239ms2026-09-15 UTC: p95 287ms2026-09-16 UTC: p95 477ms2026-09-17 UTC: p95 438ms2026-09-18 UTC: p95 392ms2026-09-19 UTC: p95 582ms2026-09-20 UTC: p95 358ms2026-09-21 UTC: p95 450ms2026-09-22 UTC: p95 353ms2026-09-23 UTC: p95 259ms2026-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 227ms
Sep 6Sep 20Oct 5
Asia-Pacific
922msp95 · 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-09-06 UTC: p95 895ms2026-09-07 UTC: p95 977ms2026-09-08 UTC: p95 942ms2026-09-09 UTC: p95 827ms2026-09-10 UTC: p95 846ms2026-09-11 UTC: p95 985ms2026-09-12 UTC: p95 886ms2026-09-13 UTC: p95 903ms2026-09-14 UTC: p95 823ms2026-09-15 UTC: p95 835ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 910ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 968ms2026-09-23 UTC: p95 902ms2026-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 922ms
Sep 6Sep 20Oct 5
US-Central
550msp95 · 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-06 UTC: p95 342ms2026-09-07 UTC: p95 357ms2026-09-08 UTC: p95 352ms2026-09-09 UTC: p95 476ms2026-09-10 UTC: p95 370ms2026-09-11 UTC: p95 588ms2026-09-12 UTC: p95 406ms2026-09-13 UTC: p95 530ms2026-09-14 UTC: p95 543ms2026-09-15 UTC: p95 632ms2026-09-16 UTC: p95 535ms2026-09-17 UTC: p95 589ms2026-09-18 UTC: p95 676ms2026-09-19 UTC: p95 674ms2026-09-20 UTC: p95 704ms2026-09-21 UTC: p95 695ms2026-09-22 UTC: p95 543ms2026-09-23 UTC: p95 525ms2026-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 550ms
Sep 6Sep 20Oct 5
Canada
297msp95 · 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-06 UTC: p95 263ms2026-09-07 UTC: p95 227ms2026-09-08 UTC: p95 292ms2026-09-09 UTC: p95 308ms2026-09-10 UTC: p95 424ms2026-09-11 UTC: p95 491ms2026-09-12 UTC: p95 471ms2026-09-13 UTC: p95 552ms2026-09-14 UTC: p95 422ms2026-09-15 UTC: p95 430ms2026-09-16 UTC: p95 410ms2026-09-17 UTC: p95 477ms2026-09-18 UTC: p95 533ms2026-09-19 UTC: p95 787ms2026-09-20 UTC: p95 807ms2026-09-21 UTC: p95 650ms2026-09-22 UTC: p95 639ms2026-09-23 UTC: p95 873ms2026-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 297ms
Sep 6Sep 20Oct 5
UK
238msp95 · 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-06 UTC: p95 234ms2026-09-07 UTC: p95 171ms2026-09-08 UTC: p95 177ms2026-09-09 UTC: p95 186ms2026-09-10 UTC: p95 175ms2026-09-11 UTC: p95 306ms2026-09-12 UTC: p95 221ms2026-09-13 UTC: p95 523ms2026-09-14 UTC: p95 204ms2026-09-15 UTC: p95 240ms2026-09-16 UTC: p95 261ms2026-09-17 UTC: p95 325ms2026-09-18 UTC: p95 188ms2026-09-19 UTC: p95 163ms2026-09-20 UTC: p95 275ms2026-09-21 UTC: p95 173ms2026-09-22 UTC: p95 256ms2026-09-23 UTC: p95 177ms2026-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 238ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · 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-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 977ms2026-09-10 UTC: p95 655ms2026-09-11 UTC: p95 566ms2026-09-12 UTC: p95 601ms2026-09-13 UTC: p95 725ms2026-09-14 UTC: p95 876ms2026-09-15 UTC: p95 951ms2026-09-16 UTC: p95 971ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 792ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 857ms2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 632ms2026-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.2s
Sep 6Sep 20Oct 5
Australia
1.3sp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 906ms2026-09-09 UTC: p95 768ms2026-09-10 UTC: p95 752ms2026-09-11 UTC: p95 897ms2026-09-12 UTC: p95 948ms2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 968ms2026-09-15 UTC: p95 956ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 781ms2026-09-21 UTC: p95 990ms2026-09-22 UTC: p95 854ms2026-09-23 UTC: p95 852ms2026-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.3s
Sep 6Sep 20Oct 5
South America
713msp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 627ms2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 871ms2026-09-10 UTC: p95 950ms2026-09-11 UTC: p95 933ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 914ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 772ms2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1s2026-09-23 UTC: p95 751ms2026-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 713ms
Sep 6Sep 20Oct 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

Get an email when we see Bunny CDN go down, and when it is back

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.

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: 202msstatus code: 200checked: Oct 5, 2026, 9:00 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
      Operationallatency: 326msstatus code: 200checked: Oct 5, 2026, 9:03 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
      Operationallatency: 299msstatus code: 200checked: Oct 5, 2026, 8:47 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
      Operationallatency: 130msstatus code: 200checked: Oct 5, 2026, 8:47 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
    Operationallatency: 464msstatus code: 200checked: Oct 5, 2026, 8:45 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 169msstatus code: 200checked: Oct 5, 2026, 9:03 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
      Operationallatency: 234msstatus code: 200checked: Oct 5, 2026, 9:01 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 638msstatus code: 200checked: Oct 5, 2026, 8:58 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
      Operationallatency: 1064msstatus code: 200checked: Oct 5, 2026, 8:51 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
      Operationallatency: 1097msstatus code: 200checked: Oct 5, 2026, 8: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 outages

Partial outage, 20mmeasured by our probes · UK2026-09-30
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
Payment Gateway Failures on Dashboard, 2h 37mdeclared on their status page2026-09-08
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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

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

Separately, we measured 19 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

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.