No impact incident

bunny.net: Security update regarding one of our infrastructure providers

Affected: CDN

Current status of bunny.net: Operational — live bunny.net status

Timeline

1. Oct 28, 2026, 11:40 UTC
   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.
2. Oct 29, 2026, 18:40 UTC
   monitoring
   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.
3. Oct 31, 2026, 12:50 UTC
   monitoring
   We've completed the reissuance of managed TLS certificates for custom domains. All managed certificates have been reissued with new private keys, and the previous certificates have been revoked. No action is required from customers using managed certificates. If you manage your own TLS certificates and haven't done so yet, we continue to recommend revoking and reissuing them with new private keys as a precaution. - What we're doing to prevent this in the future We have stopped using the affected provider while their investigation continues. We recognise that we can't rely on any single layer of security, so we're taking additional steps to reduce the potential impact of similar incidents that could occur in the future. We're reducing what each server holds: we're changing how configurations are distributed so that each PoP only receives the configuration and TLS certificates for the sites it is actively serving, limiting the data stored on any single server. Neither our investigation nor the provider's has found any evidence of unauthorized access to our server. Should anything change, we will provide an update via email and on our status page. Thank you for your patience while we completed this work. 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.
4. Nov 4, 2026, 13:38 UTC
   monitoring
   We can confirm that the revocation of all affected certificates is now complete. Let's Encrypt has published every revocation in its Certificate Revocation Lists (CRLs). Every Let's Encrypt certificate that was on the affected server has been revoked with the reason "key compromise". Browsers and clients that check revocation will now reject the old certificates. The replacement certificates now in use are not affected, and customers don't need to do anything. Our provider's investigation is still ongoing. We will continue to follow up and will share the final outcome once it is complete.

Updates as published by bunny.net (original).