Security update regarding one of our infrastructure providers

Incident Report for 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 been permanently removed from our infrastructure.

Our investigation confirmed that unauthorized SSH keys had been added to the server through the provider's virtualization layer. We found no evidence that these keys were used to access the server or perform any further actions. However, we cannot rule out the possibility that data was accessed or copied through the virtualization layer.


What this means for your data:
While our investigation has not found evidence that customer data was accessed, we cannot completely rule out the possibility.

​If data was accessed, 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). We are reissuing managed TLS certificates for custom domains and expect to complete the process 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:
At this stage, we are continuing to monitor our infrastructure closely and collaborating with the affected provider. Should any new findings affect our customers, we will provide an update via email and on our status page.

​Following two security incidents involving separate infrastructure providers in recent weeks, we are taking additional steps to reduce our exposure to third-party infrastructure risks.

​We are reviewing our reliance on third-party cloud platforms, which currently host a small portion of our CDN, and taking steps to reduce that reliance. The affected servers have already been removed from service and permanently decommissioned. We have also begun transitioning additional cloud-hosted locations and will continue evaluating the remaining environments to identify opportunities to further strengthen our infrastructure security.

​We remain committed to continuously strengthening the security and reliability of our infrastructure.

​If you have any questions or need assistance with managing your TLS certificates, our support team will be happy to help.
Posted Nov 18, 2026 - 12:25 UTC