Nationwide Speed Map
- >10s
- 3s-10s
- 1s-3s
- 0.5s-1s
- <=0.5s
33 monitoring points in this test
100%
| Region | Fastest | Slowest | Average |
|---|---|---|---|
| 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
0Showing: 33/33
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| 海外台湾高雄 | -- | 保留 | Failed | 0.012s | -- | 失败 | -- | -- | -- |
| 海外台湾台北 | -- | 保留 | Failed | 0.009s | -- | 失败 | -- | -- | -- |
| 海外香港沙田 | -- | 保留 | Failed | 0.002s | -- | 失败 | -- | -- | -- |
| 海外香港九龙 | -- | 保留 | Failed | 0.002s | -- | 失败 | -- | -- | -- |
| 海外澳门 | -- | 保留 | Failed | 0.003s | -- | 失败 | -- | -- | -- |
| 海外卡塔尔 | -- | 保留 | Failed | 0.012s | -- | 失败 | -- | -- | -- |
| 海外沙特阿拉伯 | -- | 保留 | Failed | 0.015s | -- | 失败 | -- | -- | -- |
| 海外印度 | -- | 保留 | Failed | 0.012s | -- | 失败 | -- | -- | -- |
| 海外印度尼西亚 | -- | 保留 | Failed | 0.012s | -- | 失败 | -- | -- | -- |
| 海外新加坡 | -- | 保留 | Failed | 0.020s | -- | 失败 | -- | -- | -- |
| 海外日本东京 | -- | 保留 | Failed | 0.003s | -- | 失败 | -- | -- | -- |
| 海外以色列 | -- | 保留 | Failed | 0.022s | -- | 失败 | -- | -- | -- |
| 海外韩国 | -- | 保留 | Failed | 0.015s | -- | 失败 | -- | -- | -- |
| 海外越南 | -- | 保留 | Failed | 0.019s | -- | 失败 | -- | -- | -- |
| 海外马来西亚 | -- | 保留 | Failed | 0.003s | -- | 失败 | -- | -- | -- |
| 海外菲律宾 | -- | 保留 | Failed | 0.332s | -- | 失败 | -- | -- | -- |
| 海外泰国 | -- | 保留 | Failed | 0.008s | -- | 失败 | -- | -- | -- |
| 海外韩国 | -- | 保留 | Failed | 0.001s | -- | 失败 | -- | -- | -- |
| 海外菲律宾 | -- | 保留 | Failed | 0.095s | -- | 失败 | -- | -- | -- |
| 海外英国 | -- | 保留 | Failed | 0.019s | -- | 失败 | -- | -- | -- |
| 海外芬兰 | -- | 保留 | Failed | 0.012s | -- | 失败 | -- | -- | -- |
| 海外西班牙 | -- | 保留 | Failed | 0.019s | -- | 失败 | -- | -- | -- |
| 海外德国 | -- | 保留 | Failed | 0.018s | -- | 失败 | -- | -- | -- |
| 海外法国 | -- | 保留 | Failed | 0.014s | -- | 失败 | -- | -- | -- |
| 海外波兰 | -- | 保留 | Failed | 0.013s | -- | 失败 | -- | -- | -- |
| 海外美国芝加哥 | -- | 保留 | Failed | 0.002s | -- | 失败 | -- | -- | -- |
| 海外美国华盛顿 | -- | 保留 | Failed | 0.002s | -- | 失败 | -- | -- | -- |
| 海外美国洛杉矶 | -- | 保留 | Failed | 0.002s | -- | 失败 | -- | -- | -- |
| 海外巴西 | -- | 保留 | Failed | 0.010s | -- | 失败 | -- | -- | -- |
| 海外南非 | -- | 保留 | Failed | 0.012s | -- | 失败 | -- | -- | -- |
| 海外澳大利亚 | -- | 保留 | Failed | 0.012s | -- | 失败 | -- | -- | -- |
| 海外俄罗斯莫斯科 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 海外柬埔寨金边 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
Website Speed Test Test Findings for rr1166.com
- Tested
- Sep 17, 2026, 5:44 PM
- Completed probes
- 33/33
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- 24 ms
This HTTP website speed test for rr1166.com ran on 2026-09-17. All 31 valid observation nodes returned no valid HTTP response, giving a 0% response rate, with no HTTP status codes or total response times recorded. This is a time-bound obser
rr1166.com 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
P50 total response time
Total response time (ms)
Key findings
- All 31 valid observation nodes obtained no valid HTTP response, so the response rate was 0%, below the 95% threshold.
- No HTTP status codes were collected, the 2xx count was 0, and no median or percentile total response time data exists.
- Two additional platform probe failures were excluded from observed, unavailable, and response-rate figures and do not describe the tested website.
- Telecom, Unicom, and Mobile each had 0 nodes; only overseas had 31 observations, so carrier comparison is not supported.
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.