8.8.8.8 Speed Test

Carrier
DNS

Nationwide Speed Map

Nationwide Speed Map
  • >10s
  • 3s-10s
  • 1s-3s
  • 0.5s-1s
  • <=0.5s
100%
RegionFastestSlowestAverage
All Nodes------
China Telecom------
China Unicom------
China Mobile------
East China------
South China------
Central China------
North China------
Southwest------
Northwest------
Northeast------
HK/MO/TW------

DNS Resolution Stats

1

Showing: 74/74

NodeResponse IPIP LocationStatusTotalResolveConnectDownloadRedirectHead
联通北京联通8.8.8.8Anycast/google.com//Failed10.000s--失败------
联通天津联通8.8.8.8Anycast/google.com//Failed10.000s--失败------
联通上海联通8.8.8.8Anycast/google.com//Failed10.011s--失败------
联通重庆联通8.8.8.8Anycast/google.com//Failed10.002s--失败------
联通河北邯郸联通8.8.8.8Anycast/google.com//Failed10.002s--失败------
联通河北邢台联通8.8.8.8Anycast/google.com//Failed10.007s--失败------
联通河北唐山联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通河南开封联通8.8.8.8Anycast/google.com//Failed10.011s--失败------
联通河南洛阳联通8.8.8.8Anycast/google.com//Failed10.005s--失败------
联通河南平顶山联通8.8.8.8Anycast/google.com//Failed10.004s--失败------
联通河南漯河联通8.8.8.8Anycast/google.com//Failed10.015s--失败------
联通河南商丘联通8.8.8.8Anycast/google.com//Failed10.006s--失败------
联通河南驻马店联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通河南郑州联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通河南郑州1联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通云南曲靖联通8.8.8.8Anycast/google.com//Failed10.006s--失败------
联通云南昆明联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通辽宁铁岭联通8.8.8.8Anycast/google.com//Failed10.000s--失败------
联通辽宁沈阳联通8.8.8.8Anycast/google.com//Failed10.028s0.001s0.015s0.001s----
联通辽宁抚顺联通8.8.8.8Anycast/google.com//Failed10.007s--失败------
联通辽宁鞍山联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通黑龙江鸡西联通8.8.8.8Anycast/google.com//Failed10.012s--失败------
联通湖南岳阳联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通湖南永州联通8.8.8.8Anycast/google.com//Failed10.007s--失败------
联通湖南邵阳1联通8.8.8.8Anycast/google.com//Failed10.013s0.001s0.001s0.001s----
联通湖南衡阳联通8.8.8.8Anycast/google.com//Failed10.003s--失败------
联通湖南邵阳联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通安徽芜湖联通8.8.8.8Anycast/google.com//Failed10.000s--失败------
联通安徽滁州联通8.8.8.8Anycast/google.com//Failed10.005s--失败------
联通安徽马鞍山联通8.8.8.8Anycast/google.com//Failed10.010s--失败------
联通山东龙口联通8.8.8.8Anycast/google.com//Failed10.013s--失败------
联通山东济宁联通8.8.8.8Anycast/google.com//Failed10.003s--失败------
联通山东枣庄联通8.8.8.8Anycast/google.com//Failed10.012s--失败------
联通山东青岛联通8.8.8.8Anycast/google.com//Failed10.016s--失败------
联通山东菏泽联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通江苏苏州联通8.8.8.8Anycast/google.com//Failed10.002s--失败------
联通江苏盐城联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通江苏徐州联通8.8.8.8Anycast/google.com//Failed10.012s--失败------
联通浙江宁波联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通浙江杭州联通8.8.8.8Anycast/google.com//Failed10.013s--失败------
联通浙江温州1联通8.8.8.8Anycast/google.com//Failed10.027s0.001s0.015s0.001s----
联通浙江温州联通8.8.8.8Anycast/google.com//Failed10.000s--失败------
联通浙江杭州联通8.8.8.8Anycast/google.com//Failed10.002s--失败------
联通江西南昌联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通湖北恩施联通8.8.8.8Anycast/google.com//Failed10.012s--失败------
联通广西贵港联通8.8.8.8Anycast/google.com//Failed10.002s--失败------
联通甘肃兰州联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通甘肃庆阳联通8.8.8.8Anycast/google.com//Failed10.000s--失败------
联通甘肃平凉1联通8.8.8.8Anycast/google.com//Failed10.002s--失败------
联通甘肃平凉联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通山西长治联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通山西晋中联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通山西运城联通8.8.8.8Anycast/google.com//Failed10.002s0.001s0.001s0.001s----
联通内蒙古包头联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通内蒙古赤峰联通8.8.8.8Anycast/google.com//Failed10.005s--失败------
联通陕西西安联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通陕西渭南联通8.8.8.8Anycast/google.com//Failed10.003s--失败------
联通吉林辽源联通8.8.8.8Anycast/google.com//Failed10.012s--失败------
联通吉林梅河口联通8.8.8.8Anycast/google.com//Failed10.015s--失败------
联通吉林通化联通8.8.8.8Anycast/google.com//Failed10.004s--失败------
联通福建厦门联通8.8.8.8Anycast/google.com//Failed10.002s--失败------
联通福建宁德联通8.8.8.8Anycast/google.com//Failed10.014s--失败------
联通福建福州联通8.8.8.8Anycast/google.com//Failed6.024s0.001s0.001s0.001s----
联通贵州贵阳联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通贵州黔南联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通广东清远联通8.8.8.8Anycast/google.com//Failed10.004s--失败------
联通广东佛山联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通广东韶关联通8.8.8.8Anycast/google.com//Failed10.003s--失败------
联通广东揭阳联通8.8.8.8Anycast/google.com//Failed10.005s--失败------
联通广东湛江联通8.8.8.8Anycast/google.com//Failed10.000s--失败------
联通青海西宁联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通青海西宁2联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通四川广安联通8.8.8.8Anycast/google.com//Failed10.001s--失败------
联通宁夏银川联通8.8.8.8Anycast/google.com//Failed10.000s--失败------

Website Speed Test Test Findings for 8.8.8.8

Tested
Sep 22, 2026, 1:12 AM
Completed probes
76/76
Valid HTTP response probes
0 (0%)
Average total response time
9951 ms

This HTTP website speed test ran on 2026-09-21 against 8.8.8.8. Of 74 observed nodes, none obtained a valid HTTP response, giving a 0% response rate below the 95% threshold, so no usable total response time data was collected in this observ

8.8.8.8 HTTP speed test performance by network

Valid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.

Valid HTTP response rate

Valid HTTP response rate (%)

0%Highest rate
Valid HTTP response rateValid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.050100Unicom: 0%0%Unicom

P50 total response time

Total response time (ms)

P50 total response timeValid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.050100Unicom: ----Unicom
Valid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.

Key findings

  • The unicom carrier contributed 74 observed nodes, none of which returned a valid HTTP response, for a 0% response rate against the 95% threshold.
  • Two platform probe errors were recorded and excluded from observed, unavailable, and response rate figures; they are not attributed to the tested website.
  • No HTTP status codes were recorded, http2xx count was 0, and p50, p90, p95, and average total response time all had no data.
  • Observed response IP diversity was 1, which is a time-bound observation only and does not by itself indicate anything further.

Improvement recommendations

  • The HTTP response rate is 0%, below the 95% review threshold. Retest failed probes and use their status codes or network errors to inspect the CDN, reverse proxy, or origin only if failures persist.

These results describe this distributed test only and do not establish long-term availability, security, or a root cause.