Check out my comparison of query latency across three different Umbrella datacenters.

Fantastic to see someone putting in the solid work of a 72-hour test, that's the kind of data I love to see.

One thought on your methodology - hitting the same five high-traffic domains repeatedly might mean you're mostly measuring cached responses after the first query in each batch. For catching real variance in resolver performance, especially for a new API domain, you might want to include a few unique, low-TTL subdomain queries per cycle. That forces a fresh lookup and can reveal slower recursive resolution times that caching masks.

Also, did you see any pattern where one resolver's 95th percentile latency was wildly different from the mean? That's often the real pipeline killer.