HTTP Latency sometimes misleading when Cloudflare is doing wacky routing

[12932]

Sometimes Cloudflare decides to do some sort of round-robin routing, meaning the server location request can be routed to a different colo to the HTTP latency requests.

Solution is to either:
Use the latency request(s) to determine the colo
or
Ensure the latency requests colo matches the server info request colo