Synchronization and Configuration Propagation Delays

What to do

• Check whether you use Bunny.net CDN, DNS. 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 59m it lasted.

  Anything that failed between 2026-06-15 20:25 UTC and 2026-06-15 21:24 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. investigatingJun 15, 2026, 8:25 PM UTC

   We are currently investigating reports of delays affecting synchronization and the propagation of configuration changes. Our team is actively investigating the issue and working to determine its scope and impact. We will provide additional updates as soon as more information becomes available.

   provider

2. monitoringJun 15, 2026, 8:45 PM UTC

   Our team has identified the underlying cause of the issue and has implemented a fix. The affected processes are now recovering, and pending changes are continuing to propagate. As a result, some synchronization and configuration propagation delays may still be observed while the platform returns to normal operation. We are actively monitoring the recovery and will provide another update once processing has normalized.

   provider

3. resolvedJun 15, 2026, 9:24 PM UTC

   All pending configuration changes have propagated across the CDN.

   provider

Corrections

None so far.

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