CDN configuration sync 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 1d 4h it lasted.

  Anything that failed between 2026-05-26 06:47 UTC and 2026-05-27 11:15 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

1. identifiedMay 26, 2026, 6:47 AM UTC

   We've been observing 25 to 30 nodes in various PoPs around the world exhibiting constant delays with syncing their configuration since yesterday evening. We've depooled all impacted nodes as a temporary workaround and working on a permanent fix.

   provider

2. monitoringMay 26, 2026, 4:00 PM UTC

   A fix is being staged on a subset of affected nodes. Impacted nodes are since identifying the issue isolated from CDN traffic and only receiving test traffic. Further updates will be provided after testing concludes and deployment to all affected nodes is complete.

   provider

3. resolvedMay 27, 2026, 11:15 AM UTC

   The fix has been deployed to all nodes. We will be readding the missing nodes to the pool today.

   provider

Corrections

None so far.

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