Resolved after 1 day 2 hours, affecting CDN and DNS, on May 22, 2026.
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.
Affected components
Update timeline
- investigating May 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.
- identified May 22, 2026, 02: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.
- monitoring May 22, 2026, 07: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.
- resolved May 23, 2026, 01:52 PM UTC
This incident has been resolved.
Your product runs on more than Bunny
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services