← Back to the carnage
BUNNY_CDN
🟠 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)
// The official story
Database Controller Outage
// Status page says
Aug 25 , 14:06 UTC Identified - We have identified an issue with our Database controller, that our Engineering team are working to restore. Databases already online are not affected and will continue operating normally, but idle Databases or Database management is currently unavailable.
🔗 Official status page (for the PR-approved version)
https://status.bunny.net/incidents/ftpkdhql16zsBunny_cdn's Greatest Hits
🟢 BUNNY_CDN
4d 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. (Auto-resolved: no updates in 24h)
🟢 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)