← Back to the carnage
BUNNY_CDN
⚪ A core network outage at a Frankfurt provider turned Bunny's servers into digital ghosts for 8 minutes. Telemetry confirmed the incident ended at 02:44 UTC and hasn't returned for a repeat performance. Bunny's calling it resolved because even dead networks eventually wake up.
// The official story
Network issues in Frankfurt
// Status page says
Oct 15 , 13:15 UTC Resolved - Root Cause behind this incident was a core network outage on one of our major Frankfurt providers that made a large number of Bunny servers in Frankfurt unreachable between 02:36 and 02:44 UTC. We haven't observed any further issues since 02:44 UTC, nor expect any further issues due to this and will be resolving this incident at this time. Oct 15 , 07:24 UTC <b
🔗 Official status page (for the PR-approved version)
https://status.bunny.net/incidents/f99klzgp7tbtBunny_cdn's Greatest Hits
🟢 BUNNY_CDN
Sep 03, 2026
🔴 Bunny's encoding pipeline had an existential crisis—playback died, uploads vanished into the void, and transcoding jobs forgot what they were doing. Everything's technically back online now, but your videos might be having an identity crisis about their own status. (Auto-resolved: no updates in 24h)
🟢 BUNNY_CDN
Sep 02, 2026
🟡 Bunny CDN caught in LA's network meltdown—their provider's server apparently needed a smoke break. Engineers are playing phone tag with vendors while your content takes the scenic route to users. (Auto-resolved: no updates in 24h)
🟢 BUNNY_CDN
Aug 25, 2026
🟠 Bunny's database controller decided to become a zen master—existing databases are fine, but trying to spin up new ones or manage them? That's a no-go zone right now. Engineering is caffeinating themselves into a solution. (Auto-resolved: no updates in 24h)
🟢 BUNNY_CDN
May 21, 2026
🟢 bunny.net went dark because someone forgot to pay the domain bill... internally. The registrar had to manually resurrect it, and now we're all waiting for DNS to stop being petulant. (Auto-resolved: no updates in 24h)