все же индусы были ни при чем, это был внутренний мисконфиг 🤷

The service topology for the 1.1.1.1 Resolver's prefixes was reduced from all locations down to a single, offline location.

Once our configuration error had been exposed and Cloudflare systems had withdrawn the routes from our routing table, all of the 1.1.1.1 routes should have disappeared entirely from the global Internet routing table. However, this isn’t what happened with the prefix 1.1.1.0/24. Instead, we got reports from Cloudflare Radar that Tata Communications India (AS4755) had started advertising 1.1.1.0/24: from the perspective of the routing system, this looked exactly like a prefix hijack. This was unexpected to see while we were troubleshooting the routing problem, but to be perfectly clear: this BGP hijack was not the cause of the outage. We are following up with Tata Communications.

https://blog.cloudflare.com/cloudflare-1-1-1-1-incident-on-july-14-2025/

спасибо за ежегодный аудит реданданси, пойду фолбек днс провайдера поставлю