bunny.net Outage History

bunny.net experienced degraded performance in their Singapore region for 1.3 hours, affecting CDN, Edge Storage, Magic Containers, and Database services. The issue was caused by an outage with an upstream network provider. The incident was resolved after the upstream provider fixed their network issue, and bunny.net monitored the situation before confirming full resolution.

Bunny.net experienced configuration delays affecting CDN Pull Zones for 7.4 hours due to a large-scale domain sync that began around 00:15 UTC. The core issue was resolved at 06:00 UTC, with the backlog of delayed configuration changes fully cleared by 09:30 UTC. The engineering team has identified the root cause and will implement measures to prevent future occurrences.

bunny.net experienced increased response times and timeouts on their Statistics API endpoint for 12.8 hours, affecting both the dashboard and direct API requests for CDN and DNS statistics reporting. The engineering team identified an overloaded process on the statistics endpoint as the root cause and implemented a fix. The issue was resolved after monitoring confirmed the fix was effective.

The bunny.net Statistics API endpoint experienced increased response times for 3.2 hours, causing delayed reports and timeouts when accessing CDN statistics through both the dashboard and direct API requests. The issue affected the API component and was resolved after implementing a fix to the statistics backend. Users experienced delays in retrieving statistics data and some requests timing out during the incident period.

Bunny.net's Stream transcoding service experienced delays in video processing due to high demand on their free encoding services over 85.2 hours. Only free encoding was affected, while premium encoding, existing videos, and delivery continued to operate normally. The issue was resolved by expanding transcoding capacity, which cleared the delays and normalized processing times.

bunny.net's Magic Containers platform experienced deployment delays and failures for 3.4 hours due to unintended CPU throttling on new pod and application deployments caused by a recent deployment. The Containers team identified the root cause and implemented mitigating changes to prevent recurrence.

bunny.net experienced log forwarding failures that affected all zones configured with log forwarding functionality, while standard logging remained operational. The engineering team implemented a fix after 13.3 hours and monitored the results before confirming full resolution.

bunny.net's CDN log delivery platform experienced delays due to growth exceeding the system's original design capacity over several weeks. The service affected customers' ability to receive logs in a timely manner, with delivery delays occurring across the platform. The issue was resolved by migrating to a new, more robust logging platform, though the migration had to be accelerated and resulted in temporarily reduced log retention (1.5 days instead of the usual 3 days) while the system rebuilt its full retention capacity.

bunny.net experienced delays in processing pull zone configuration updates affecting their API, CDN, and Stream Service for 2.1 hours. Existing configurations and platform traffic continued to operate normally during the incident. The engineering team applied a fix to process the backlog of delayed configurations and resolved the issue.