rewindex

ChangesBunny.netSecurity update regarding one of our infrastructure providers

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

Silent editNot classified yetChanged status.bunny.net (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

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.

ChangedUpdatemonitoring#1
Before: Update - 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.
After: 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.

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.

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

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayThursday, October 29Thu, Oct 29

1 rewrite, 1 incident change

All Bunny.net changesBunny.net profileMarkdownJSON