Security update regarding one of our infrastructure providers
bunny.net reports a security incident at one of its infrastructure providers. One CDN node in Pakistan was on an affected server, but that node was out of traffic rotation and did not serve requests. bunny.net removed the server and the status is monitoring.
State
Monitoring
Started
Ongoing for
50 min
Worst impact
Notice
Timeline
1 updateMonitoring
50 min 100%
Updates
Times in UTCAs posted by bunny.net
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. Incident Summary: On November 17, an infrastructure provider reported unauthorized access involving third-party server management software. One bunny.net CDN node in Pakistan was hosted on an affected server. The node in question had already been out of traffic rotation for over a week due to ongoing network maintenance and was not serving requests. Our engineering team took immediate action. The affected node had already been out of traffic rotation for over a week and was not actively serving requests due to ongoing maintenance related to regional network stability issues. Within 8 minutes of receiving the alert, we removed the server from our system entirely. 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
bunny.net in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
39
Median duration
3 h 48 min
This incident
78% shorter than the median
Other bunny.net incidents
All incidentsbunny.net·Network unavailability in Los Angeles
Network unavailability in Los Angeles affected bunny.net CDN, Edge Storage, Magic Containers, and Bunny Database. Bunny.net reports that CDN traffic was rerouted to the nearest PoP. The incident is resolved and lasted about 14 hours and 17 minutes.
bunny.net·Shield Zone Update Failures
bunny.net reports that Shield Zone updates failed on the API and Bunny Shield components. A fix is in place and bunny.net monitors the result. The incident is resolved after 44 minutes.
bunny.net·Crypto Payment Failures
Crypto payments fail on the bunny.net API. The partner payment provider stopped its service after a security incident. Bunny.net investigates the issue. Crypto payments and pending payments continue when the partner starts its service again. Other payment methods and all bunny.net services work normally.
bunny.net·Degraded API Response Times
bunny.net reported degraded API response times that affected the Dashboard and API. The incident is resolved and lasted about 61 minutes.
bunny.net·Security update regarding one of our infrastructure providers
bunny.net reported a security incident that affected the CDN. bunny.net now states that the incident is resolved. The incident lasted from 28 October 2026 to 9 November 2026.
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.
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.
https://outages.live/feed.xml?providers=bunny/feed subscribe https://outages.live/feed.xml?providers=bunnyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane