- Level
- confirmed
- Worst impact
- Degraded
- Components
- CDN Logging
- Down Index
- 24of 100
What to do
Check whether you use Bunny.net CDN Logging. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 9h 57m it lasted.
Anything that failed between 2026-10-05 23:02 UTC and 2026-10-06 08:58 UTC may need a replay.Subscribe to Bunny.net's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=bunny works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Bunny.net 3
- investigating
We're investigating performance degradation within our CDN Logging infrastructure, impacting our CDN Logging offering.
provider
- monitoring
A suboptimal log query had put a lot of load to an infrastructure component affecting performance of the whole system. The query has been isolated. We're observing better throughput, but will be monitoring the situation for the next few hours.
provider
- resolved
This incident has been resolved
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d74bf1516e
Is Bunny.net still down?
No, this incident was resolved 2026-10-06 08:58 UTC. For Bunny.net's live state, see https://down.guide/bunny.
How long did it last?
9h 57m, from 2026-10-05 23:02 UTC to 2026-10-06 08:58 UTC, by the times Bunny.net posted.
What was affected?
Bunny.net named CDN Logging.
What caused it?
Bunny.net hasn't published a root cause. If it does, it shows here.
Where does this come from?
Bunny.net's official status page, https://status.bunny.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.