Tons of big ISPs and content providers peer in KC but AT&T skips them all and appears to backhaul all Kansas traffic to DFW before doing any peering. Side note: I wish AT&T was better about peering outside of their major transit POPs and better about building smaller POPs in regional hubs. Go with the one with the least censorship, best security, and most privacy.

Once you're at the exchange point, it doesn't really matter which provider you choose. My point is, low latencies to datacenter-located resolver clients is great but the advantage is reduced when consumer internet users have to go across their ISP's long private fiber hauls to get to a POP. I suspect that Cloudflare and Google DNS both have POPs in Dallas, which accounts for the similar numbers to my private resolver. I'm getting ~26ms to 1.1.1.1 and ~19ms to my private DNS resolver that I host in a datacenter in Dallas. I'm in a small town in Kansas, connected by 1 Gbit ATT fiber. Residential customers won't see anything this fast. Where are you testing from? I'm going to guess: a datacenter.

Opendns dnscrypt pfsense 2.4