← Back to the carnage
BUNNY_CDN

🟡 Bunny CDN found out the hard way that Frankfurt's network infrastructure has an expiration date. Stream, uploads, and storage are playing hide-and-seek with users' content. Engineering team currently playing detective with a network issue that nobody asked for. (Auto-resolved: no updates in 24h)

⏰ Jan 28, 2026 Fixed (for now) spotted via status_rss

// The official story

Stream API/Upload, Storage and CDN Partial Outage

// Status page says

Jan 28 , 23:39 UTC Investigating - We identified a network issue pertaining to our Stream and Storage (Frankfurt) platform. CDN services with Frankfurt storage may have been partially affected. We are currently investigating the problem.

🔗 Official status page (for the PR-approved version)

https://status.bunny.net/incidents/k8zjzbrlz0m2

Bunny_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)