google.com IPv6 Speed Test

Carrier
Node Type
IPv6

IPv6 网站测速

通过 IPv6 网络检测网站解析、连接和下载响应时间

Nationwide Speed Map

Nationwide Speed Map
  • >10s
  • 3s-10s
  • 1s-3s
  • 0.5s-1s
  • <=0.5s
100%
RegionFastestSlowestAverage
All Nodes山西运城 0.009s山西大同 0.035s0.022s
China Telecom------
China Unicom山西运城 0.009s山西运城 0.009s0.009s
China Mobile山西大同 0.035s山西大同 0.035s0.035s
East China------
South China------
Central China------
North China山西运城 0.009s山西大同 0.035s0.022s
Southwest------
Northwest------
Northeast------
HK/MO/TW------

DNS Resolution Stats

29

Showing: 92/92

NodeResponse IPIP LocationStatusTotalResolveConnectDownloadRedirectHead
电信重庆江津::保留Failed0.008s0.000s0.000s0.000s----
电信河北唐山::保留Failed0.008s0.000s0.000s0.000s----
电信河南驻马店::保留Failed0.003s0.000s0.000s0.000s----
电信云南昆明::保留Failed0.005s0.000s0.000s0.000s----
电信湖南邵阳2607:f8b0:400e:c06::64美国/Oregon/The Dalles/谷歌Failed10.003s0.002s0.000s0.000s----
电信安徽池州2607:f8b0:400e:c0d::66美国/Oregon/The Dalles/谷歌Failed10.012s0.011s0.000s0.000s----
电信浙江宁波2607:f8b0:400e:c07::66美国/Oregon/The Dalles/谷歌Failed10.104s0.103s0.000s0.000s----
电信江西吉安2607:f8b0:400e:c1e::8a美国/Oregon/The Dalles/谷歌Failed10.028s0.027s0.000s0.000s----
电信广西贵港::保留Failed0.031s0.000s0.000s0.000s----
电信广西南宁::保留Failed0.003s0.000s0.000s0.000s----
电信广西柳州::保留Failed0.010s0.000s0.000s0.000s----
电信甘肃庆阳1::保留Failed0.080s0.000s0.000s0.000s----
电信山西晋中::日本/Kanagawa/Yokohama/KDDIFailed0.003s0.002s0.000s0.000s----
电信内蒙古包头::保留Failed0.019s0.000s0.000s0.000s----
电信陕西西安1::保留Failed0.007s0.000s0.000s0.000s----
电信陕西渭南::保留Failed0.069s0.000s0.000s0.000s----
电信陕西西安::保留Failed0.054s0.000s0.000s0.000s----
电信吉林松原2607:f8b0:400e:c1e::66美国/Oregon/The Dalles/谷歌Failed10.008s0.007s0.000s0.000s----
电信贵州黔南2606:4700:20::681a:594美国/California/San Francisco/CloudflareFailed0.255s0.002s0.224s0.001s----
电信广东佛山::保留Failed0.041s0.000s0.000s0.000s----
电信广东清远::保留Failed0.008s0.000s0.000s0.000s----
电信广东广州::保留Failed0.007s0.000s0.000s0.000s----
电信青海海东::保留Failed0.002s0.000s0.000s0.000s----
电信西藏拉萨2607:f8b0:400e:c1e::64美国/Oregon/The Dalles/谷歌Failed10.064s0.063s0.000s0.000s----
电信四川成都::保留Failed0.007s0.000s0.000s0.000s----
电信宁夏银川2607:f8b0:400e:c05::64美国/Oregon/The Dalles/谷歌Failed10.043s0.041s0.000s0.000s----
电信海南海口2607:f8b0:400e:c1e::66美国/Oregon/The Dalles/谷歌Failed10.042s0.041s0.000s0.000s----
联通重庆::保留Failed0.014s0.000s0.000s0.000s----
联通河北唐山::保留Failed0.022s0.000s0.000s0.000s----
联通河南驻马店::保留Failed0.011s0.000s0.000s0.000s----
联通河南郑州::保留Failed0.002s0.000s0.000s0.000s----
联通河南信阳::保留Failed0.027s0.000s0.000s0.000s----
联通云南昆明::保留Failed0.020s0.000s0.000s0.000s----
联通辽宁盘锦::保留Failed0.003s0.000s0.000s0.000s----
联通湖南岳阳::保留Failed0.006s0.000s0.000s0.000s----
联通湖南邵阳::保留Failed0.002s0.000s0.000s0.000s----
联通山东枣庄::保留Failed0.005s0.000s0.000s0.000s----
联通江苏南京2404:6800:4008:c02::71中国/台湾/台北/谷歌Failed10.006s0.004s0.000s0.000s----
联通浙江宁波2404:6800:4008:c19::8a中国/台湾/台北/谷歌Failed10.012s0.011s0.000s0.000s----
联通江西南昌2404:6800:4008:c03::8a中国/台湾/台北/谷歌Failed10.012s0.011s0.000s0.000s----
联通湖北恩施::保留Failed0.000s0.000s0.000s0.000s----
联通广西贵港::保留Failed0.008s0.000s0.000s0.000s----
联通甘肃庆阳::保留Failed0.082s0.000s0.000s0.000s----
联通甘肃平凉1::保留Failed0.001s0.000s0.000s0.000s----
联通甘肃平凉::保留Failed0.042s0.000s0.000s0.000s----
联通山西晋中::1日本/Kanagawa/Yokohama/KDDIFailed0.005s0.003s0.000s0.000s----
联通山西运城::1日本/Kanagawa/Yokohama/KDDI2000.009s0.004s0.001s0.001s1次
联通陕西西安::保留Failed0.004s0.000s0.000s0.000s----
联通陕西渭南::保留Failed0.069s0.000s0.000s0.000s----
联通吉林辽源::保留Failed0.048s0.000s0.000s0.000s----
联通福建厦门2404:6800:4008:c05::71中国/台湾/台北/谷歌Failed10.006s0.004s0.000s0.000s----
联通贵州黔南::保留Failed0.010s0.000s0.000s0.000s----
联通贵州贵阳::保留Failed0.002s0.000s0.000s0.000s----
联通广东清远::保留Failed0.013s0.000s0.000s0.000s----
联通广东佛山::保留Failed0.019s0.000s0.000s0.000s----
联通广东广州::保留Failed0.007s0.000s0.000s0.000s----
联通青海海东::保留Failed0.002s0.000s0.000s0.000s----
联通宁夏银川1::保留Failed0.007s0.000s0.000s0.000s----
移动重庆江津::保留Failed0.006s0.000s0.000s0.000s----
移动重庆沙坪坝::保留Failed0.007s0.000s0.000s0.000s----
移动河北唐山12404:6800:4008:c04::65中国/台湾/台北/谷歌Failed10.015s0.013s0.000s0.000s----
移动河北唐山2404:6800:4008:c01::64中国/台湾/台北/谷歌Failed10.024s0.021s0.000s0.000s----
移动河南漯河2404:6800:4008:c02::71中国/台湾/台北/谷歌Failed10.010s0.009s0.000s0.000s----
移动河南驻马店2404:6800:4008:c01::71中国/台湾/台北/谷歌Failed10.031s0.029s0.000s0.000s----
移动河南信阳2404:6800:4008:c07::8a中国/台湾/台北/谷歌Failed10.026s0.022s0.000s0.000s----
移动云南昆明::保留Failed0.022s0.000s0.000s0.000s----
移动湖南邵阳2404:6800:4008:c02::64中国/台湾/台北/谷歌Failed10.009s0.008s0.000s0.000s----
移动安徽池州2404:6800:4008:c00::8b中国/台湾/台北/谷歌Failed10.053s0.013s0.000s0.000s----
移动安徽合肥2404:6800:4008:c05::71中国/台湾/台北/谷歌Failed10.030s0.029s0.000s0.000s----
移动山东聊城2404:6800:4008:c04::66中国/台湾/台北/谷歌Failed10.011s0.009s0.000s0.000s----
移动山东菏泽2404:6800:4008:c04::65中国/台湾/台北/谷歌Failed10.015s0.013s0.000s0.000s----
移动新疆伊犁2404:6800:4008:c03::66中国/台湾/台北/谷歌Failed10.027s0.023s0.000s0.000s----
移动浙江宁波2404:6800:4008:c00::66中国/台湾/台北/谷歌Failed10.012s0.011s0.000s0.000s----
移动浙江金华2404:6800:4008:c01::66中国/台湾/台北/谷歌Failed10.010s0.009s0.000s0.000s----
移动江西宜春2404:6800:4008:c13::8b中国/台湾/台北/谷歌Failed10.017s0.016s0.000s0.000s----
移动广西贵港::保留Failed0.030s0.000s0.000s0.000s----
移动广西南宁::保留Failed0.005s0.000s0.000s0.000s----
移动广西柳州::保留Failed0.012s0.000s0.000s0.000s----
移动甘肃庆阳2404:6800:4008:c1b::8b中国/台湾/台北/谷歌Failed10.018s0.017s0.000s0.000s----
移动山西晋中::1日本/Kanagawa/Yokohama/KDDIFailed0.006s0.005s0.000s0.000s----
移动山西大同::1日本/Kanagawa/Yokohama/KDDI2000.035s0.015s0.001s0.001s1次
移动陕西西安12404:6800:4008:c06::71中国/台湾/台北/谷歌Failed10.029s0.028s0.000s0.000s----
移动陕西渭南2404:6800:4008:c07::64中国/台湾/台北/谷歌Failed10.276s0.274s0.000s0.000s----
移动福建厦门2404:6800:4008:c02::66中国/台湾/台北/谷歌Failed10.005s0.004s0.000s0.000s----
移动贵州黔南::保留Failed5.016s0.000s0.000s0.000s----
移动广东清远::保留Failed0.018s0.000s0.000s0.000s----
移动广东佛山::保留Failed0.026s0.000s0.000s0.000s----
移动广东湛江::保留Failed0.016s0.000s0.000s0.000s----
移动广东广州::保留Failed0.009s0.000s0.000s0.000s----
移动四川广安::保留Failed0.037s0.000s0.000s0.000s----
移动宁夏银川2404:6800:4008:c13::64中国/台湾/台北/谷歌Failed10.007s0.006s0.000s0.000s----
移动宁夏中卫2404:6800:4008:c19::8a中国/台湾/台北/谷歌Failed10.010s0.008s0.000s0.000s----

IPv6 Website Speed Test Test Findings for google.com

Tested
Oct 6, 2026, 12:52 PM
Completed probes
92/92
Valid IPv6 HTTP response probes
2 (2.2%)
Average IPv6 total response time
22 ms

This IPv6 HTTP test of google.com ran on 2026-10-06 across 92 nodes. Only 2 nodes obtained a valid IPv6 HTTP response, giving an IPv6 response rate of 2.2%, well below the 95% reference threshold. The median IPv6 total response time among r

google.com IPv6 speed test performance by network

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

Valid IPv6 response rate

Valid IPv6 response rate (%)

3.2%Highest rate
Valid IPv6 response rateValid IPv6 response rate counts probes with an IPv6 HTTP status and total response time. P50 is the total time at or below which half of valid responses completed.050100Telecom: 0%0%TelecomUnicom: 3.2%3.2%UnicomMobile: 2.9%2.9%Mobile

P50 IPv6 total response time

IPv6 total response time (ms)

9 msLowest P50
P50 IPv6 total response timeValid IPv6 response rate counts probes with an IPv6 HTTP status and total response time. P50 is the total time at or below which half of valid responses completed.02550Telecom: ----TelecomUnicom: 9 ms9 msUnicomMobile: 35 ms35 msMobile
Valid IPv6 response rate counts probes with an IPv6 HTTP status and total response time. P50 is the total time at or below which half of valid responses completed.

Key findings

  • Only 2 of 92 nodes returned a valid IPv6 HTTP response; 90 nodes did not obtain a valid result as defined for this test, for an IPv6 response rate of 2.2%.
  • All observed IPv6 status codes were 200, seen twice, with no other status codes and a node error count of 0.
  • Among responding nodes, the median IPv6 total response time was 22 ms, with p90 at 32 ms and p95 at 34 ms.
  • Observed IPv6 response-address diversity was 30 unique addresses, and response counts differed by carrier: telecom had 0 of 27 nodes respond, unicom 1 of 31, and mobile 1 of 34.

Improvement recommendations

  • The IPv6 HTTP response rate is 2.2%, below the 95% review threshold. Retest failed probes and verify the AAAA record, IPv6 route, firewall, and CDN or origin IPv6 support only if failures persist.

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