- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 22of 100
What to do
Check whether you use Bunny.net API. 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 4h 5m it lasted.
Anything that failed between 2026-02-06 09:56 UTC and 2026-02-06 14:01 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 are currently investigating a delay in configurations on CDN pull zones, DNS, Scripting Storage or Stream libraries propagating to our network. Existing configurations and CDN/Stream traffic are not affected.
provider
- monitoring
We have identified the root cause of the configuration delays. There is now currently a backlog of configurations to process, we will continue to monitor the situation.
provider
- resolved
The configuration delay has now 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-bc8f08cef2
Is Bunny.net still down?
No, this incident was resolved 2026-02-06 14:01 UTC. For Bunny.net's live state, see https://down.guide/bunny.
How long did it last?
4h 5m, from 2026-02-06 09:56 UTC to 2026-02-06 14:01 UTC, by the times Bunny.net posted.
What was affected?
Bunny.net named API.
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.