rewindex

ChangesBunny.netSecurity update regarding one of our infrastructure providers

Bunny.net: Incident updated: Security update regarding one of our infrastructure providers

Incident updateDownplayed?Normal progress (rule, 100%)Changed status.bunny.net (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Downplayed?

Vendor rated this none; a Hacker News thread about it drew 224 points and 45 comments. Bunny CDN Security Incident (opens in new tab)

This is an automated signal, not a finding. It compares the vendor’s own impact rating with public Hacker News activity (points, comments in the first hour, distinct commenters, first-hand symptom reports). HN users skew technical, so the impact on any one customer may differ. How this is computed.

Incident page: the full timeline of updates

What changed

Struck in red is what Bunny.net removed; blue is what they added. Muted text is unchanged context.

AddedUpdatemonitoring#1
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Monday, November 9

1 incident change

Wednesday, November 4

1 incident change

Saturday, October 31

1 incident change

Thursday, October 29

1 rewrite, 1 incident change

Cite this

Incident updated: Security update regarding one of our infrastructure providers on Bunny.net’s status page, changed 2026-10-31 12:53 UTC (change 3 of 5).

Title
Incident updated: Security update regarding one of our infrastructure providers
Vendor
Bunny.net
Date
URL
https://rewindex.com/change/r212be59954eb61

All Bunny.net changesBunny.net profileMarkdownJSON