CloudPing.info

[moooofly]

https://www.cloudping.info/

Amazon Web Services™ are available in several regions. Click the button below to estimate the latency from your browser to each AWS™ region.

读图：

• 这里显示的 latency 是从你的本地浏览器到 AWS 全球各个 region 的测试数据；
• 测试方式为 HTTP Ping

Region	Latency
US-East (Virginia) 弗吉尼亚州	310 ms
US East (Ohio) 俄亥俄州	322 ms
US-West (California) 加利福尼亚州	306 ms
US-West (Oregon) 俄勒冈州	277 ms
Canada (Central) 加中	314 ms
Europe (Ireland) 爱尔兰	330 ms
Europe (London) 伦敦	237 ms
Europe (Frankfurt) 法兰克福	407 ms
Europe (Paris) 巴黎	232 ms
Europe (Stockholm) 斯德哥尔摩	541 ms
Asia Pacific (Mumbai) 孟买	408 ms
Asia Pacific (Osaka-Local) 大阪	406 ms
Asia Pacific (Seoul) 首尔	196 ms
Asia Pacific (Singapore) 新加坡	99 ms
Asia Pacific (Sydney) 悉尼	233 ms
Asia Pacific (Tokyo) 东京	192 ms
South America (São Paulo) 圣保罗	419 ms
China (Beijing) 北京	36 ms
China (Ningxia) 宁夏	62 ms
AWS GovCloud (US-East) 政府云	326 ms
AWS GovCloud (US) 政府云	293 ms

• Central Canada (sometimes the Central provinces) is a region consisting of Canada's two largest and most populous provinces: Ontario and Quebec.
• Ontario 安大略省
• Quebec 魁北克市

[moooofly]

相关链接

• AWS GovCloud：Amazon把美国政府带至“云”上
• Timing breakdown phases explained
• 地域和可用区

[moooofly]

问题

• 仅提供了测试结果，测试结论得到的方法不知道，因为无法确定其准确性；
  • [x] 测试方法：利用 dynamodb 的 ping 接口
  • [x] 准确性：仅发起两次请求，第一次用于“解决HTTPS连接建立耗时问题”，第二次作为最终结果；可以认为测试结果并不准确；
• 仅提供一次性测试结果，历史数据比较只能自己采样后对比；
• 仅提供测试数据，没有关于距离的图示，没法直观感受距离和延迟之间的关联；

[moooofly]

原理分析

• 运行一次测试的整体情况

• 增加随机数并利用 404 resp 计算 latency

同一个 region 第一次测试

同一个 region 第二次测试

两次测试的主要差别

• 不加随机数的情况

直接访问 https://dynamodb.us-east-1.amazonaws.com/ping

[moooofly]

Timing breakdown phases explained

Here's more information about each of the phases you may see in the Timing tab:

• Queueing. The browser queues requests when:
  • There are higher priority requests.
  • There are already six TCP connections open for this origin, which is the limit. Applies to HTTP/1.0 and HTTP/1.1 only.
  • The browser is briefly allocating space in the disk cache
• Stalled. The request could be stalled for any of the reasons described in Queueing.
• DNS Lookup. The browser is resolving the request's IP address.
• Proxy negotiation. The browser is negotiating the request with a proxy server.
• Request sent. The request is being sent.
• ServiceWorker Preparation. The browser is starting up the service worker.
• Request to ServiceWorker. The request is being sent to the service worker.
• Waiting (TTFB). The browser is waiting for the first byte of a response. TTFB stands for Time To First Byte. This timing includes 1 round trip of latency and the time the server took to prepare the response.
• Content Download. The browser is receiving the response.
• Receiving Push. The browser is receiving data for this response via HTTP/2 Server Push.
• Reading Push. The browser is reading the local data previously received.