These aren't even data centers, but aggregates. They're regions, composed of many different bits of networking and compute in various levels of abstraction - dc, edge installation, whatever.

Within these regions there's a lot of variation from zone to zone, so the methodology matters.

Author here. This is great feedback, thanks.

Idea: select a data center by default (i.e. us-east-1) to make it more clear.

Bonus: select the nearest data center based on the user’s IP :)

Nitpick detail: us-east-1 (and all other availability zones) are also not a single datacenter by definition. The can also spend several

I appreciate the effort to collect the data, but I think the rotating globe is an idea that looks cool, but makes the visualization harder to use. If I click on us-east-1, there's a 229ms line to...somewhere that I can't see. Meanwhile, I can't see the latency between us-east-1 and us-east-2.

Perhaps if you selected a datacenter, and it switched to a 2-d projection with that datacenter at the center of the map, it would be better?

Or perhaps augment the visualization with a table?

Winkel Tripel projection would mitigate this nicely.

(One of several options, though the best IMO.)

<https://en.wikipedia.org/wiki/Winkel_tripel_projection>

Author here - You can see the raw data as a table here: https://www.cloudping.co. Sometimes visualizations like this are a careful act of balancing practicality with cool-factor.