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

> Incident updated: Security update regarding one of our infrastructure providers. Detected 2026-10-31 by Rewindex: what changed on Bunny.net’s status page, with the before/after diff.

Canonical: https://rewindex.com/change/r212be59954eb61
Last updated: 2026-10-31T12:53:43Z

**Summary:** _summary pending_
- Kind: Incident update · Label: Normal progress (rule)
- Changed: 2026-10-31 12:53 UTC · Detected: 2026-10-31 12:53 UTC
- [Source: https://status.bunny.net/incidents/p6gf1by9kr7m](https://status.bunny.net/incidents/p6gf1by9kr7m)
- [Company: Bunny.net](https://rewindex.com/company/bunny-net.md)
- Versions: before incident\_version:81/p6gf1by9kr7m@96feaef1668a → after incident\_version:81/p6gf1by9kr7m@8ca417cfc5a9
- Change 3 of 5 for this incident

## Downplayed?

Vendor rated this none; a Hacker News thread about it drew 224 points and 45 comments. [Bunny CDN Security Incident](https://news.ycombinator.com/item?id=50308697)

_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. Method: [About: Hacker News signals](https://rewindex.com/about#signals)_
Incident page (full timeline): [Security update regarding one of our infrastructure providers](https://rewindex.com/company/bunny-net/incidents/p6gf1by9kr7m.md)
## What changed

**1. Added: Update** (monitoring) · 2026-10-31 12:50 UTC

```diff
+ 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.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-10-29 18:43 UTC | [Incident updated: Security update regarding one of our infrastructure providers](https://rewindex.com/change/r5a1e486088127b.md) | Normal progress |
| 2026-10-29 20:03 UTC | [Incident silently edited: Security update regarding one of our infrastructure providers](https://rewindex.com/change/r1feb9b6617c6ae.md) | Wording only |
| 2026-10-31 12:53 UTC | Incident updated: Security update regarding one of our infrastructure providers (this change) | Normal progress |
| 2026-11-04 13:43 UTC | [Incident updated: Security update regarding one of our infrastructure providers](https://rewindex.com/change/r5583ba72bcea72.md) | Normal progress |
| 2026-11-09 20:33 UTC | [Incident updated: Security update regarding one of our infrastructure providers](https://rewindex.com/change/rcd2127c61b271c.md) | Normal progress |

Previous: [change](https://rewindex.com/change/r1feb9b6617c6ae.md) · Next: [change](https://rewindex.com/change/r5583ba72bcea72.md) · All Bunny.net changes: [timeline](https://rewindex.com/company/bunny-net/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._

## 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).

- Canonical URL: https://rewindex.com/change/r212be59954eb61
- Citation: Bunny.net, “Incident updated: Security update regarding one of our infrastructure providers” (2026-10-31 12:53 UTC). Archived by Rewindex: https://rewindex.com/change/r212be59954eb61 (CC BY 4.0).
- Markdown link: `[Bunny.net: Incident updated: Security update regarding one of our infrastructure providers (2026-10-31)](https://rewindex.com/change/r212be59954eb61)`


---
Canonical: https://rewindex.com/change/r212be59954eb61 · Markdown: https://rewindex.com/change/r212be59954eb61.md · JSON: https://rewindex.com/api/v1/changes/r212be59954eb61 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-11T04:59:09.069Z