CDN Acceleration 502s on DNS Records

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 1d 2h it lasted.

  Anything that failed between 2026-05-22 11:19 UTC and 2026-05-23 13:52 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 4

1. investigatingMay 22, 2026, 11:19 AM UTC

   As a continuation of our DNS issues last night, we are currently investigating an issue when newly CDN accelerating a DNS record results in CDN 502s for the domain in question. Existing pull zones and pull zones not created via CDN Acceleration are not affected. Existing CDN Accelerated zones are also not affected.

   provider

2. identifiedMay 22, 2026, 2:22 PM UTC

   We have identified a discrepancy in our backend process that has caused zone id mismatch on new CDN Accelerated zones. The team are currently working to deploy a hotfix to address the problem.

   provider

3. monitoringMay 22, 2026, 7:03 PM UTC

   A fix has been applied and we're now working through the backlog to process all pending updates. We expect processing to be back to real-time in the next 6 hours.

   provider

4. resolvedMay 23, 2026, 1:52 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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