The underlying issue has been fixed, and all affected DNS zones have been correctly republished. CNAME flattening is now functioning normally. In some cases, resolvers may have cached the earlier incorrect (empty) result. Where this happened, it can take a little longer for the correct records to reappear. How long depends on the negative caching settings configured for that specific zone, but this should resolve on its own without any action needed. We apologize for the disruption this caused and thank you for your patience.
Posted Aug 28, 2026 - 16:07 CEST
Monitoring
We've identified the root cause of the disruption. An internal fault caused two of our system components to become stuck waiting on each other, which prevented the lookups needed for CNAME flattening from completing. As a result, affected zones were mistakenly republished without the expected address records, causing resolution failures. Our team has resolved the underlying fault and is now republishing the affected zones with the correct records. We expect all zones to be fully operational within the hour. We will post a final update once service is confirmed fully restored.
Posted Aug 28, 2026 - 14:28 CEST
Update
We are continuing to investigate this issue.
Posted Aug 28, 2026 - 13:41 CEST
Investigating
We are currently experiencing an issue with our CNAME flattening service, which is temporarily unavailable. This may affect DNS resolution for domains relying on this feature.
Our engineering team is working on a solution, and we will post updates here as soon as we have more information.
We apologize for any inconvenience this may cause.
Posted Aug 28, 2026 - 13:40 CEST
This incident affected: DNS Infrastructure (DNS Unicast Network, DNS Anycast Network).