Live

Security update regarding one of our infrastructure providers

0

bunny.net reports an issue that affects the CDN. All managed TLS certificates for custom domains are reissued with new private keys, and the old certificates are revoked. bunny.net keeps the incident under monitoring.

A language model wrote this summary from the updates of bunny.net.

State

Monitoring

Started

4 d ago

2026-10-28 11:40 UTC

Ongoing for

4 days

Worst impact

Notice

Timeline

1 update
Oct 28Oct 29Oct 30Oct 31Nov 1
NoticeUpdate postedDates in UTC

Monitoring

4 days 100%

Updates

Times in UTC

As posted by bunny.net

Monitoring2026-10-31 21:45 UTC

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 n

Affected components

1
CDN

bunny.net in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

5

Median duration

Not enough data

This incident

Not comparable

Follow bunny.net

Your coding agent knows when bunny.net is down, and tells you when a failure is theirs, not yours. You can also get bunny.net incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "bunny" and tell me if bunny.net has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=bunny
Slack
/feed subscribe https://outages.cc/feed.xml?providers=bunny

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane