Bunny.net: Configuration change delays

What to do

Check whether you use Bunny.net CDN. 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 7h 20m it lasted.
Anything that failed between 2026-05-01 03:51 UTC and 2026-05-01 11:12 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.

investigatingMay 1, 2026, 3:51 AM UTC
We are currently investigating issues related to delayed configuration of Pull Zones.
provider
identifiedMay 1, 2026, 8:43 AM UTC
We have identified the core issue at hand and our Engineering team are currently reviewing the situation. Configuration delays/syncs are slowly recovering.
provider
resolvedMay 1, 2026, 11:12 AM UTC
The configuration delay has now been resolved. At around 00:15, we observed a large scale domain sync that caused configuration delays. This was resolved at 06:00 UTC, before the backlog of configuration changes were cleared by 09:30 UTC. Our Engineering team have identified the core issue and will take action to prevent future recurrence of the problem.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Bunny.net still down?

No, this incident was resolved 2026-05-01 11:12 UTC. For Bunny.net's live state, see https://down.guide/bunny.

How long did it last?

7h 20m, from 2026-05-01 03:51 UTC to 2026-05-01 11:12 UTC, by the times Bunny.net posted.

What was affected?

Bunny.net named CDN.

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.