Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

bunny.net Outage History

Every past bunny.net outage tracked by IsDown, with detection times, duration, and resolution details.

There were 169 bunny.net outages since July 2020. The 44 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 30, 2026

March 2026: Increased Response Times for Statistics Reporting

Detected Mar 30, 2026 5:05 AM EDT · Resolved Mar 30, 2026 5:53 PM EDT · Duration about 13 hours

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.

Minor March 26, 2026

March 2026: Increased Response Times for Statistics Reporting

Detected Mar 26, 2026 12:16 PM EDT · Resolved Mar 26, 2026 3:25 PM EDT · Duration about 3 hours

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.

Minor March 23, 2026

March 2026: Delays in Video Processing on Stream

Detected Mar 23, 2026 3:50 PM EDT · Resolved Mar 27, 2026 5:04 AM EDT · Duration 4 days

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.

Minor March 19, 2026

March 2026: Container Application Update Issues

Detected Mar 19, 2026 7:41 AM EDT · Resolved Mar 19, 2026 11:07 AM EDT · Duration about 3 hours

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.

Minor March 5, 2026

March 2026: Log Forwarding Failures

Detected Mar 5, 2026 10:29 AM EST · Resolved Mar 5, 2026 11:45 PM EST · Duration about 13 hours

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.

Minor March 3, 2026

March 2026: CDN Log Delivery Delay

Detected Mar 3, 2026 5:12 AM EST · Resolved Mar 4, 2026 9:32 AM EST · Duration 1 day

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.

Minor March 2, 2026

March 2026: Delayed Zone Configuration Updates

Detected Mar 2, 2026 4:18 AM EST · Resolved Mar 2, 2026 6:22 AM EST · Duration about 2 hours

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.