Live

Security update regarding one of our infrastructure providers

0

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 update
12:2512:3812:5013:0313:15
NoticeUpdate postedTimes in UTC

Monitoring

50 min 100%

Updates

Times in UTC

As posted by bunny.net

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. 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 history
90 days agoToday

Incidents in 90 days

20

Days with an incident

39

Median duration

3 h 48 min

This incident

78% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 days
median 3 h 48 min
90 days agoToday

Other bunny.net incidents

All incidents

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane