This is interesting! I found the screenshot table intriguing on its own, actually. Some of these you guys had mentioned previously, like how small Denver is, but others I wouldn’t have guessed. E.g., the huge spare capacity in Los Angeles (particularly in comparison to San Francisco).
A few small enhancements that come to mind, that might be nice in the future, 
…
- Column (or at least JSON field) for the cost multiplier, which is currently only available by parsing the pricing page’s HTML.
- All-pairs round-trip times (RTT) might get a bit bulky for most clients, but maybe opt-in via an
?rtt=all-pairs. - An indicator, even a simple one, of the recent extent of host failures and failed synthetic alerts—conditions that fall short of a full notification in the existing status system, but might inform people’s decisions when they’re on the fence about latency, cost, etc.
(These are classic feeds for optimization/placement algorithms, in other industries.)