outages.live
Live

bunny.net

bunny.net is operational

Checked 2 min ago Operational

Security update regarding one of our infrastructure providers

bunny.net reports a security problem with one of its infrastructure providers. The problem affects CDN managed TLS certificates for custom domains. bunny.net has reissued all managed certificates with new private keys and revoked the previous certificates. The status is monitoring.

Noticeupdated 2 d ago

History

90 days agoToday

Incidents in 90 days

16

Days with an incident

24

Median duration

3 h 19 min

Longest incident

4 days

Components

17
Website Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days ago2 days with an incidentToday
API Operational
90 days ago1 day with an incidentToday
CDN Operational
90 days ago10 days with an incidentToday
DNS Operational
90 days agoNo incidentsToday
Edge Storage Operational
90 days ago4 days with an incidentToday
Optimizer Operational
90 days ago2 days with an incidentToday
Origin Shield Operational
90 days agoNo incidentsToday
Bunny Fonts Operational
90 days agoNo incidentsToday
Edge Scripting Operational
90 days agoNo incidentsToday
Magic Containers Operational
90 days ago2 days with an incidentToday
Bunny Shield Operational
90 days agoNo incidentsToday
Bunny Database Operational
90 days ago4 days with an incidentToday
CDN Logging Operational
90 days ago2 days with an incidentToday

Stream

Stream Service Operational
90 days ago3 days with an incidentToday
Stream - Transcoding Service Operational
90 days ago7 days with an incidentToday
Live Stream Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 24, 2026

Duration1 h 58 min18:45 to 20:43Performance degradation in DENotice

This incident has been resolved, we're not observing performance issues anymore.

Oct 15, 2026

Duration13 h 10 min21:09 to 10:19Storage operations in DE and Stream uploads performance degradationDegraded

This issue has now been resolved.

Duration10 h 31 min02:44 to 13:15Network issues in FrankfurtNotice

Root Cause behind this incident was a core network outage on one of our major Frankfurt providers that made a large number of Bunny servers in Frankfurt unreachable between 02:36 and 02:44 UTC. We haven't observed any further issues since 02:44 UTC, nor expect any further issues due to this and will be resolving this incident at this time.

Oct 7, 2026

Duration12 h 23 min10:13 to 22:36Database Performance DegradationDegraded

This incident has now been resolved.

Oct 5, 2026

Duration9 h 57 min23:02 to 08:58CDN Log forwarding performance degradationDegraded

This incident has been resolved

Sep 25, 2026

Duration2 h 25 min14:49 to 17:15Degraded Optimizer Response timesDegraded

A subset of optimizer workers exhibited disk performance issues, impacting Optimizer software's throughput. A fix has been deployed to all servers sharing this same hardware model and performance is back at normal levels again.

Sep 22, 2026

Duration30 min13:37 to 14:07Intermittent Login/API Timeouts in PolandDegraded

Network performance issues caused by an upstream provider have been mitigated via traffic rerouting. All services and connection timeouts have returned to normal.

Sep 21, 2026

Duration3 h 19 min19:34 to 22:53CDN Synchronization DelaysDegraded

This incident has been resolved.

Sep 17, 2026

Duration4 days20:31 to 09:17Increased encoding processing timeDegraded

Video encoding delays have now been fully resolved.

Sep 8, 2026

Duration2 h 37 min15:47 to 18:24Payment Gateway Failures on DashboardDegraded

The issue affecting payment attempts on the billing dashboard has been resolved. Our monitoring has confirmed that the service is operating normally.

Sep 3, 2026

Duration1 h 51 min13:47 to 15:38Video Playback and Encoding Failures on Bunny StreamPartial outage

This issue is now fully resolved. Our Engineering team have identified additional guardrails to prevent this specific issue from happening in future.

Duration4 h 18 min08:53 to 13:11Network issues in Los AngelesDegraded

This incident has been resolved.

Sep 2, 2026

Duration1 h 12 min14:38 to 15:51Network issues in Los AngelesDegraded

A wider network incident in Los Angeles impacted Bunny Services hosted in the region. Affected network providers have mitigated the incident and all impacted services have remained stable since then.

Aug 25, 2026

Duration8 h 24 min14:06 to 22:31Database Controller OutageDegraded

After monitoring the affected services, we have confirmed that Database management and idle Database activation are operating normally.

Maintenance

Storage, Database and Magic Containers Network Maintenance Notice (Sydney)

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

Maintenancestarts in 18 d

Follow bunny.net

Your coding agent knows when bunny.net is down, and tells you when a failure is theirs, not yours. You can also get bunny.net incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "bunny" and tell me if bunny.net has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=bunny
Slack
/feed subscribe https://outages.live/feed.xml?providers=bunny

Go from tracking outages to fixing production issues with Polylane.

Try Polylane