Live / bunny.net / Incident
bunny.net: CDN Log forwarding performance degradation
bunny.net · bunny.netMinor incidentResolved2026-10-06 08:58 UTC
Public — what happened
Summary
bunny.net reported slower performance in its CDN logging system, which affected its CDN Logging service, starting at 23:02 UTC on October 5, 2026. By 00:07 UTC on October 6, the company said an inefficient log query had placed heavy strain on part of its infrastructure and slowed the whole system, and that the query had been separated out. bunny.net said throughput was improving and kept watching the system. The incident was marked resolved at 08:58 on October 6.
Affected
CDN Logging
Timeline
- Started — 2026-10-05 23:02 UTC
- Investigating — 2026-10-05 23:02 UTC
- Monitoring — 2026-10-06 00:07 UTC
- Resolved — 2026-10-06 08:58 UTC · 9h 57m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach bunny.net against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for bunny.net: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the bunny.net report →
More from bunny.net
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.