BUNNY_CDN

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

⏰ Sep 02, 2026 Fixed (for now) spotted via status_rss

// The official story

Network issues in Los Angeles

// Status page says

Sep 2 , 14:38 UTC Investigating - We're investigating reports of widespread network issues in Los Angeles that seem to be impacting our services as well. We are working with our providers in the area to understand the issue at hand and mitigate.

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

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

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

🟢 BUNNY_CDN May 14, 2026

🟠 Some genius's upstream provider decided to take an unscheduled sabbatical, leaving Singapore users staring at loading spinners. Bunny claims it's 'resolved' but is definitely refreshing the monitoring dashboard every 30 seconds. (Auto-resolved: no updates in 24h)