← Back to the carnage
BUNNY_CDN
⚪ BunnyCDN's Singapore node went full ghost mode, then got resurrected faster than you can say 'Southeast Asia traffic reroute.' Engineers identified the gremlin, deployed the fix, and now we're all pretending that 30-minute blackout never happened. (Auto-resolved: no updates in 24h)
// The official story
Singapore CDN & Storage Network Outage
// Status page says
Jan 15 , 22:58 UTC Resolved - This incident has been resolved. Jan 15 , 22:39 UTC Monitoring - A fix has been implemented, and we are monitoring. Jan 15 , 22:28 UTC Identified - We are currently investigating connectivity issues affecting our Singapore location. CDN traffic will be re-balancing to other locati
🔗 Official status page (for the PR-approved version)
https://status.bunny.net/incidents/m34sk8cnvp35Bunny_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)