[spacebacon]

Hmm... Who just changed their dns vs. riding it out?

[sirius87]

I was in the midst of migrating my namecheap domain from Route53 to Cloudflare. Set up all the DNS records while ignoring the /api/ errors shown at the bottom of the Cloudflare dashboard thinking some ad block setting in my browser was messed up.

Then I realised setting the NS in Namecheap to Cloudflare's nameservers was taking an inordinate amount of time to propagate, and that's when I checked X/Twitter. Set it back to Route53.

[burcs]

We did, we were slowly working towards migrating to AWS entirely and this just helped expedite it.

[issafram]

It hasn't affected my home network at all. I use their DNS servers and nothing has resolving addresses has not stopped working

[0x0000000]

Parent comment was likely referring to authoritative DNS, not Cloudflare's public resolvers.

[dogweather]

I'm planning my transition away for 10 or so subdomains and 30 records.

The only feature I need to research in new providers is: access to Whois ASN numbers, which I insert into HTTP request headers. I use this to tailor my site for .gov and .edu users.