- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on Bunny.net. 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 1h 39m it lasted.
Anything that failed between 2026-02-04 10:58 UTC and 2026-02-04 12:37 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 2
- identified
We are aware of and working on a fix for CDN Log Delivery delay due to a backlog in the delivery process. We will be monitoring the situation as the fix is applied.
provider
- resolved
A fix has now been applied and near real-time log delivery has now been restored. There is separately a backlog of requests that is being processed (but does not affect current real-time logs delivered).
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-495c1d1abb
Is Bunny.net still down?
No, this incident was resolved 2026-02-04 12:37 UTC. For Bunny.net's live state, see https://down.guide/bunny.
How long did it last?
1h 39m, from 2026-02-04 10:58 UTC to 2026-02-04 12:37 UTC, by the times Bunny.net posted.
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.