Nationwide Speed Map
- >10s
- 3s-10s
- 1s-3s
- 0.5s-1s
- <=0.5s
124 monitoring points in this test
100%
| Region | Fastest | Slowest | Average |
|---|---|---|---|
| All Nodes | 浙江丽水电信 0.136s | 江苏南京电信 5.885s | 0.931s |
| China Telecom | 浙江丽水电信 0.136s | 江苏南京电信 5.885s | 0.931s |
| China Unicom | -- | -- | -- |
| China Mobile | -- | -- | -- |
| East China | 浙江丽水电信 0.136s | 江苏南京电信 5.885s | 1.082s |
| South China | 广西南宁电信 0.178s | 海南三亚电信 1.763s | 0.972s |
| Central China | 湖南邵阳电信 0.153s | 湖北襄阳电信 0.790s | 0.435s |
| North China | 河北唐山电信 0.216s | 北京电信 1.7781s | 0.837s |
| Southwest | 贵州黔南电信 0.217s | 西藏拉萨1电信 2.687s | 1.059s |
| Northwest | 宁夏银川电信 0.309s | 电信青海 2.6967s | 1.155s |
| Northeast | 辽宁盘锦电信 0.215s | 辽宁沈阳电信 0.572s | 0.340s |
| HK/MO/TW | -- | -- | -- |
DNS Resolution Stats
6Showing: 121/121
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| 电信北京电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.009s | 0.008s | 失败 | -- | -- | -- |
| 电信北京电信 | 146.75.45.42 | 新加坡/Fastly, Inc. | 200 | 1.7781s | 0.3345s | 1.443s | 0.0001s | -- | |
| 电信天津电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.019s | 0.013s | 失败 | -- | -- | -- |
| 电信上海徐汇电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 10.406s | 0.006s | 0.399s | 0.001s | -- | -- |
| 电信上海奉贤电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 12.436s | 0.011s | 2.424s | 0.001s | -- | -- |
| 电信上海黄浦电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 12.442s | 0.009s | 2.431s | 0.001s | -- | -- |
| 电信重庆黔江电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.262s | 0.306s | 0.291s | 0.666s | -- | |
| 电信重庆江津电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.392s | 0.179s | 0.104s | 0.109s | -- | |
| 电信重庆两江电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 2.273s | 0.038s | 0.266s | 1.969s | -- | |
| 电信河北石家庄电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.364s | 0.215s | 0.072s | 0.078s | -- | |
| 电信河北邢台电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.231s | 0.020s | 0.103s | 0.108s | -- | |
| 电信河北唐山电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.216s | 0.020s | 0.095s | 0.100s | -- | |
| 电信河北电信 | 199.232.161.42 | 日本/东京都/东京/Fastly, Inc. | 200 | 0.4588s | 0.294s | 0.1642s | 0.0001s | -- | |
| 电信河南三门峡电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 11.596s | 0.297s | 1.284s | 0.001s | -- | -- |
| 电信河南商丘电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.028s | 0.027s | 失败 | -- | -- | -- |
| 电信河南郑州电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.020s | 0.019s | 失败 | -- | -- | -- |
| 电信河南开封电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 12.294s | 0.027s | 2.262s | 0.001s | -- | -- |
| 电信河南驻马店电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.032s | 0.031s | 失败 | -- | -- | -- |
| 电信河南漯河电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.035s | 0.033s | 失败 | -- | -- | -- |
| 电信河南南阳电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.042s | 0.034s | 失败 | -- | -- | -- |
| 电信河南信阳电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.036s | 0.034s | 失败 | -- | -- | -- |
| 电信云南昆明电信 | 151.101.89.42 | 日本/ Inc./大阪/Fastly | 200 | 1.072s | 0.479s | 0.299s | 0.294s | -- | |
| 电信云南文山电信 | 151.101.89.42 | 日本/ Inc./大阪/Fastly | 200 | 0.621s | 0.066s | 0.273s | 0.282s | -- | |
| 电信辽宁辽阳电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.450s | 0.254s | 0.096s | 0.101s | -- | |
| 电信辽宁铁岭电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.317s | 0.112s | 0.104s | 0.101s | -- | |
| 电信辽宁沈阳电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.572s | 0.042s | 0.115s | 0.416s | -- | |
| 电信辽宁鞍山电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.225s | 0.026s | 0.102s | 0.097s | -- | |
| 电信辽宁盘锦电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.215s | 0.026s | 0.090s | 0.099s | -- | |
| 电信黑龙江鸡西电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.263s | 0.036s | 0.110s | 0.117s | -- | |
| 电信湖南郴州电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.025s | 0.024s | 失败 | -- | -- | -- |
| 电信湖南长沙电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.022s | 0.020s | 失败 | -- | -- | -- |
| 电信湖南衡阳电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.036s | 0.034s | 失败 | -- | -- | -- |
| 电信湖南株洲电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.029s | 0.021s | 失败 | -- | -- | -- |
| 电信湖南邵阳电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.153s | 0.002s | 0.073s | 0.079s | -- | |
| 电信岳阳电信电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.035s | 0.034s | 失败 | -- | -- | -- |
| 电信安徽池州电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.019s | 0.018s | 失败 | -- | -- | -- |
| 电信安徽滁州电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.020s | 0.016s | 失败 | -- | -- | -- |
| 电信安徽黄山电信 | 151.101.65.42 | Anycast/fastly.com// | 200 | 4.164s | 0.007s | 1.076s | 3.082s | -- | |
| 电信安徽安庆电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.028s | 0.018s | 失败 | -- | -- | -- |
| 电信安徽淮南电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.019s | 0.015s | 失败 | -- | -- | -- |
| 电信安徽合肥电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.018s | 0.016s | 失败 | -- | -- | -- |
| 电信安徽马鞍山电信 | 151.101.89.42 | 日本/ Inc./大阪/Fastly | 200 | 1.081s | 0.494s | 0.271s | 0.257s | -- | |
| 电信安徽合肥电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.014s | 0.013s | 失败 | -- | -- | -- |
| 电信安徽芜湖电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 11.375s | 0.014s | 1.360s | 0.001s | -- | -- |
| 电信山东青岛1电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.026s | 0.025s | 失败 | -- | -- | -- |
| 电信山东枣庄电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.028s | 0.025s | 失败 | -- | -- | -- |
| 电信山东济南电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.026s | 0.025s | 失败 | -- | -- | -- |
| 电信山东龙口电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.031s | 0.027s | 失败 | -- | -- | -- |
| 电信山东青岛电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.031s | 0.024s | 失败 | -- | -- | -- |
| 电信山东枣庄电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.026s | 0.024s | 失败 | -- | -- | -- |
| 电信新疆乌鲁木齐电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.731s | 0.058s | 0.334s | 0.340s | -- | |
| 电信江苏苏州电信 | 146.75.45.42 | 新加坡/fastly.com// | 200 | 0.479s | 0.317s | 0.085s | 0.077s | -- | |
| 电信江苏宿迁电信 | -- | 保留 | Failed | 10.001s | -- | 失败 | -- | -- | -- |
| 电信江苏盐城电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.031s | 0.029s | 失败 | -- | -- | -- |
| 电信江苏泰州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.179s | 0.010s | 1.086s | 0.083s | -- | |
| 电信江苏连云港电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.027s | 0.026s | 失败 | -- | -- | -- |
| 电信江苏徐州电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.035s | 0.020s | 失败 | -- | -- | -- |
| 电信江苏无锡电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.040s | 0.030s | 失败 | -- | -- | -- |
| 电信江苏南通电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.021s | 0.020s | 失败 | -- | -- | -- |
| 电信江苏南京电信 | 146.75.113.42 | 日本/东京/fastly.com/ | 200 | 5.885s | 0.009s | 0.374s | 5.502s | -- | |
| 电信浙江宁波电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.469s | 0.279s | 0.055s | 0.134s | -- | |
| 电信浙江杭州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.398s | 0.242s | 0.226s | 0.929s | -- | |
| 电信浙江嘉兴电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.007s | 0.016s | 0.110s | 0.881s | -- | |
| 电信浙江绍兴电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.185s | 0.020s | 0.078s | 0.087s | -- | |
| 电信浙江衢州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.386s | 0.018s | 0.070s | 0.298s | -- | |
| 电信浙江丽水电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.136s | 0.032s | 0.042s | 0.062s | -- | |
| 电信江西南昌电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.998s | 0.727s | 0.088s | 0.182s | -- | |
| 电信江西吉安电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.188s | 0.054s | 0.064s | 0.070s | -- | |
| 电信江西赣州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.361s | 0.322s | 0.038s | 0.001s | -- | |
| 电信湖北十堰电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.643s | 0.151s | 0.244s | 0.249s | -- | |
| 电信湖北武汉电信 | 151.101.1.42 | 美国/ Inc.//Fastly | Failed | 10.007s | 0.001s | 0.001s | 0.001s | -- | -- |
| 电信湖北咸宁电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.156s | 0.027s | 0.060s | 0.070s | -- | |
| 电信湖北襄阳电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.790s | 0.023s | 0.235s | 0.532s | -- | |
| 电信广西贵港电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.418s | 0.250s | 0.081s | 0.087s | -- | |
| 电信广西南宁电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.178s | 0.025s | 0.073s | 0.080s | -- | |
| 电信广西南宁1电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.651s | 0.020s | 0.178s | 1.453s | -- | |
| 电信广西玉林电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.203s | 0.037s | 1.089s | 0.077s | -- | |
| 电信广西柳州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.284s | 0.030s | 0.071s | 0.183s | -- | |
| 电信甘肃兰州电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 10.720s | 0.303s | 0.415s | 0.001s | -- | -- |
| 电信甘肃平凉电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.043s | 0.042s | 失败 | -- | -- | -- |
| 电信甘肃武威电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.040s | 0.039s | 失败 | -- | -- | -- |
| 电信甘肃庆阳电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.046s | 0.046s | 失败 | -- | -- | -- |
| 电信山西晋中电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.239s | 0.014s | 0.286s | 0.938s | -- | |
| 电信内蒙古呼和浩特电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.636s | 0.295s | 0.261s | 1.080s | -- | |
| 电信内蒙古巴彦淖尔电信 | 146.75.45.42 | 新加坡/fastly.com// | 200 | 0.566s | 0.012s | 0.270s | 0.285s | -- | |
| 电信内蒙古包头电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.451s | 0.026s | 1.125s | 0.300s | -- | |
| 电信内蒙古呼和浩特电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.430s | 0.028s | 0.187s | 0.194s | -- | |
| 电信陕西西安1电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.038s | 0.028s | 失败 | -- | -- | -- |
| 电信陕西咸阳电信 | 151.101.89.42 | 日本/ Inc./大阪/Fastly | 200 | 1.313s | 0.476s | 0.369s | 0.468s | -- | |
| 电信陕西渭南电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.038s | 0.037s | 失败 | -- | -- | -- |
| 电信陕西西安电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.028s | 0.028s | 失败 | -- | -- | -- |
| 电信吉林辽源电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.037s | 0.032s | 失败 | -- | -- | -- |
| 电信吉林松原电信 | -- | 保留 | Failed | 10.001s | -- | 失败 | -- | -- | -- |
| 电信福建福州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.758s | 0.425s | 0.163s | 0.169s | -- | |
| 电信福建厦门电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.554s | 0.358s | 0.089s | 0.106s | -- | |
| 电信福建漳州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.533s | 0.061s | 0.083s | 1.387s | -- | |
| 电信福建三明电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.416s | 0.069s | 0.080s | 0.267s | -- | |
| 电信福建宁德电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.180s | 0.023s | 0.074s | 0.082s | -- | |
| 电信福建泉州电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.289s | 0.024s | 0.087s | 0.179s | -- | |
| 电信贵州贵阳电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.623s | 0.048s | 0.174s | 0.402s | -- | |
| 电信贵州黔南电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.217s | 0.046s | 0.078s | 0.094s | -- | |
| 电信贵州贵阳电信 | 199.232.161.42 | 日本/东京都/东京/Fastly, Inc. | 200 | 0.7757s | 0.4041s | 0.3706s | 0.0002s | -- | |
| 电信广东揭阳电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.033s | 0.028s | 失败 | -- | -- | -- |
| 电信广东佛山电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.016s | 0.014s | 失败 | -- | -- | -- |
| 电信广东清远电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.014s | 0.013s | 失败 | -- | -- | -- |
| 电信广东湛江电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.019s | 0.018s | 失败 | -- | -- | -- |
| 电信广东广州电信 | 146.75.113.42 | 日本/东京/fastly.com/ | Failed | 3.011s | 0.011s | 失败 | -- | -- | -- |
| 电信青海西宁电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.587s | 0.074s | 0.259s | 0.253s | -- | |
| 电信青海海东电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.291s | 0.040s | 0.248s | 1.003s | -- | |
| 电信电信青海 | 199.232.161.42 | 日本/东京都/东京/Fastly, Inc. | 200 | 2.6967s | 0.0356s | 1.5468s | 1.1139s | -- | |
| 电信西藏拉萨1电信 | 151.101.89.42 | 日本/ Inc./大阪/Fastly | 200 | 2.687s | 0.838s | 1.285s | 0.565s | -- | |
| 电信西藏拉萨电信 | 151.101.89.42 | 日本/ Inc./大阪/Fastly | Failed | 3.058s | 0.056s | 失败 | -- | -- | -- |
| 电信西藏山南电信 | 151.101.89.42 | 日本/ Inc./大阪/Fastly | 200 | 0.657s | 0.066s | 0.293s | 0.297s | -- | |
| 电信四川成都电信 | 146.75.45.42 | 新加坡/fastly.com// | 200 | 0.885s | 0.402s | 0.235s | 0.247s | -- | |
| 电信四川自贡电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.244s | 0.042s | 0.104s | 0.099s | -- | |
| 电信四川绵阳电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.751s | 0.043s | 1.094s | 0.614s | -- | |
| 电信四川广安电信 | 199.232.161.42 | 日本/东京都/东京/Fastly, Inc. | 200 | 1.3732s | 0.9925s | 0.3776s | 0.0015s | -- | |
| 电信宁夏银川电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 0.309s | 0.066s | 0.112s | 0.131s | -- | |
| 电信宁夏中卫电信 | 199.232.161.42 | 日本/东京/fastly.com/ | Failed | 3.028s | 0.028s | 失败 | -- | -- | -- |
| 电信海南三亚电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.763s | 0.622s | 1.072s | 0.069s | -- | |
| 电信海南海口电信 | 199.232.161.42 | 日本/东京/fastly.com/ | 200 | 1.305s | 0.039s | 0.073s | 1.192s | -- |
Website Speed Test Test Findings for zh.khanacademy.org
- Tested
- Oct 25, 2026, 10:57 PM
- Completed probes
- 124/124
- Valid HTTP response probes
- 67 (55.4%)
- Average total response time
- 931 ms
This HTTP website speed test ran on 2026-10-25 against zh.khanacademy.org. Of 121 observed nodes, 67 returned a valid HTTP response, a 55.4% response rate below the 95% threshold. Median total response time was 621 ms, with P90 at 1756 ms a
zh.khanacademy.org 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 (%)
55.4%Highest rate
P50 total response time
Total response time (ms)
621 msLowest P50
Key findings
- 67 of 121 observed nodes returned a 2xx valid HTTP response while 54 did not, giving a 55.4% response rate flagged as a critical low-response-rate issue.
- Every valid response carried HTTP status code 200; no other status codes appeared, so returned responses were consistent at the status level.
- Total response time was 621 ms at the median, 1756 ms at P90 and 2563 ms at P95, with a 931 ms average, so tail latency sits well above the median.
- Valid responses came from 6 distinct response IPs, an observed response IP diversity of 6; 3 platform probe failures were excluded from observed nodes and response rate.
Improvement recommendations
- The HTTP response rate is 55.4%, 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.