← 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)
// 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/k8zjzbrlz0m2Bunny_cdn's Greatest Hits
🔴 BUNNY_CDN
18h ago
🟠 Turns out LA's power grid doesn't have a failover. Bunny's LA infrastructure took an unscheduled nap, forcing CDN traffic into emergency relocation. Some servers are back online; others are still meditating on their mortality.
🟢 BUNNY_CDN
Oct 15, 2026
⚪ 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. (Auto-resolved: no updates in 24h)
🟢 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)