CDN Acceleration 502s on DNS Records

This incident has been resolved.

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.

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.

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.