Bunny.net logo

Is Bunny.net Down?

CDN & EdgeLive status, outages, and incident history

No. Bunny.net is up right now.

Every monitored Bunny.net system is operational as of October 30, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Bunny.net breaks

Bunny.net is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Bunny.net status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Bunny.net Component Status

The main Bunny.net systems on this page. All 19 are operational right now.

19operational
API
Operational
Bunny Database
Operational
Bunny Fonts
Operational

16 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Bunny Shield, CDN, CDN Logging, Dashboard, DNS, Edge Scripting, Edge Storage, Magic Containers, Optimizer, Origin Shield, Stream - Transcoding Service, Stream Service, and 4 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Bunny.net Outages & Incidents

Incident history from the official Bunny.net status page, including resolution updates.

Storage, Database and Magic Containers Network Maintenance Notice (Sydney)Scheduled for Nov 20, 2026 · 8h 0mScheduled

We will be performing a maintenance to replace a faulty hardware part in our network that will temporarily affect access to files stored in non-replicated storage zones, Magic Container and Database workloads running in Sydney. Expected Impact During the maintenance window, requests for files in non-replicated storage zones may result in temporary 5xx errors. Replicated files will remain fully accessible. For Magic Containers and Bunny Database, single-location workloads in Sydney will experience a period of unavailability. Maintenance Window Date: November 20th Time: 13:00 - 21:00 (UTC +0) Expected Impact Duration: Up to 60 minutes

Security update regarding one of our infrastructure providersStarted Oct 28, 2026Investigating

We're providing an update on the reissuance of managed TLS certificates for custom domains. Reissuance is ongoing and progressing steadily. To avoid any disruption to the delivery of your content, certificates are being reissued gradually in controlled batches, and each reissued certificate uses a new private key. This is taking longer than our initial estimate, and we now expect the process to be completed by the end of October 31. Your existing certificates continue to be served without interruption until they are replaced, and no action is required from customers using managed certificates. If you manage your own TLS certificates, we continue to recommend revoking and reissuing them with new private keys as a precaution. Neither our investigation nor the provider's ongoing investigation has found any new evidence of unauthorized access to our server. We'll post a further update on our status page once reissuance is complete. If you have any questions or need help with managing your TLS certificates, our support team will be happy to assist. --- [2026-10-28T11:40:08.286Z] (monitoring) We're reaching out to inform you of a security incident involving one of our infrastructure providers, the steps we've taken, and what this means for you. - What happened and how we responded Last week, one of our infrastructure providers reported unauthorized access involving third-party server management software. One of our CDN nodes, located in Armenia, was hosted on a server supplied by this provider. After receiving the alert from the affected provider, our engineering team took immediate action. Within 20 minutes, we stopped routing traffic through the server. We then reviewed and preserved the relevant security logs for investigation, securely wiped the server, and revoked its access to our other systems. The affected server has been permanently removed from our infrastructure. Our investigation found no evidence of unauthorized access to the CDN node or any of its data. The infrastructure provider has also found no evidence that our server was accessed, but continues to investigate the incident. - What this means for your data While neither investigation has found any indication of unauthorized access to our server, we cannot completely rule out the possibility. If unauthorized access to our CDN node did occur, the potentially exposed information would have been: temporarily cached CDN content, Pull Zone configurations, and TLS certificates stored on that server. As an additional precaution, we have revoked and reissued all TLS certificates for bunny.net platform domains (b-cdn.net and bunny.run). Reissuance of managed TLS certificates for custom domains is ongoing and is expected to be completed within the next 24 hours. No action is required from customers using managed certificates. We will post a further update on our status page once this process is complete. If you manage your own TLS certificates, we recommend revoking and reissuing them with new private keys as a precaution. No other customer data, including bunny.net account data, was stored on the server in question, and no internal systems were affected. - What happens next We’re closely monitoring our infrastructure and working with the affected provider as the investigation continues. Should any new findings affect our customers, we will provide an update via email and on our status page. At bunny.net, we understand the trust you place in us to keep your content secure, and we take that responsibility seriously. If you have any questions or need help with managing your TLS certificates, our support team will be happy to assist.

Performance degradation in DEResolved Oct 24, 2026 · 1h 19mResolved

This incident has been resolved, we're not observing performance issues anymore. --- [2026-10-24T21:24:58.080Z] (monitoring) We've found and resolved the issue and are actively monitoring performance. --- [2026-10-24T21:21:35.633Z] (investigating) We are currently investigating this issue affecting the CDN performance in DE.

Bunny.net Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Bunny.net incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 1100.00% average · 17 days with incidentsOct 30

Going further back: Bunny.net uptime by month and every recorded Bunny.net outage.

Live Bunny.net Outage Reports

Problems reported by engineers using Bunny.net. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Bunny.net problems reported yet.

Something wrong with Bunny.net on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Bunny.net

Bunny.net offers CDN, edge storage, and streaming products for delivering web and media content globally. Disruptions can affect asset delivery and edge-cached traffic. Track Bunny. status and outages here.

Over the past 30 days, PulsAPI has measured Bunny.net uptime at 100.00%. Response times, incident history, and SLA tracking for Bunny.net are available on the PulsAPI dashboard.

Bunny.net Status FAQ

Is Bunny.net down right now?

The verdict at the top of this page comes from the latest poll of the official Bunny.net status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Bunny.net is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Bunny.net recovers.

How do I check Bunny.net uptime history?

PulsAPI tracks Bunny.net uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Bunny.net changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Bunny.net outages?

PulsAPI reads the official Bunny.net status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Bunny.net components?

Yes. PulsAPI monitors 19 individual Bunny.net components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Bunny.net goes down?

Yes. Create a free account and subscribe to Bunny.net: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Bunny.net to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Bunny.net problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Bunny.net?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Bunny.net plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Bunny.net with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services