← Back to the carnage
BUNNY_CDN

🔴 One of Bunny's German storage boxes ate the dust, leaving API and CDN users holding their breath. Replication? Never heard of her. Engineering team is doing their best impression of a disk recovery specialist. (Auto-resolved: no updates in 24h)

⏰ Feb 20, 2026 Fixed (for now) spotted via status_rss

// The official story

Disk Failure in Frankfurt

// Status page says

Feb 20 , 16:13 UTC Identified - We currently are experiencing an outage with one server within our German storage array. There may be isolated timeouts from Storage API, as well as timeouts on CDN, where no replication is enabled, or where some assets are uncached on the CDN network. Our Engineering team are working to restore the server.

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

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

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)