On July 14, Cloudflare's 1.1.1.1 Resolver service experienced an outage affecting users worldwide. The cause was attributed to a misconfiguration related to preparations for a new Data Localization Suite service. An internal error related to the configuration of legacy systems inadvertently led to the disruption. This error had been dormant until a change to the service on July 14, which triggered a global configuration refresh affecting users' ability to access internet services through the 1.1.1.1 Resolver.
Cloudflare's 1.1.1.1 Resolver service became unavailable to the internet starting at 21:52 UTC and ending at 22:54 UTC. The majority of 1.1.1.1 users globally were affected. For many users, not being able to resolve names using the 1.1.1.1 Resolver meant that basically all Internet services were unavailable.
The outage was caused by a misconfiguration of legacy systems which are used to uphold the infrastructure advertising Cloudflare's IP addresses to the internet.
This configuration error sat dormant in the production network as the new DLS service was not yet in use, but it set the stage for the outage on July 14.
Cloudflare added an offline datacenter location to the service topology for the pre-production DNS service in order to allow for some internal testing.
Collection
[
|
...
]