Nationwide Speed Map
- >10s
- 3s-10s
- 1s-3s
- 0.5s-1s
- <=0.5s
12 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: 12/12
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| 电信贵州贵阳电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信湖北十堰电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信苏州电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信四川广安电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信河北电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信北京电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 联通甘肃联通 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 联通上海数据中心 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 海外俄罗斯莫斯科 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 海外柬埔寨金边 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 海外迪拜 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信电信青海 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
Website Speed Test Test Findings for 8629486.cc
- Tested
- Sep 15, 2026, 3:35 PM
- Completed probes
- 12/12
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- --
This HTTP website speed test for 8629486.cc on 2026-09-10 covered 314 observed nodes, with a 97.1% response rate, a median total response time of 1364 ms and an average of 1859 ms. Overseas latency was notably higher, and 12 HTTP 502 respon
There is not enough network HTTP speed-test data to draw this chart.
Key findings
- Of 314 observed nodes, 305 returned a valid HTTP response, giving a 97.1% response rate; 9 nodes did not obtain a valid result. Platform probe errors were 0 and are excluded from website performance.
- HTTP status codes comprised 292 responses with 200, 1 with 204 and 12 with 502; the 502 count exceeds the threshold of 0 and represents server error responses observed in this test.
- Overseas nodes showed a median total response time of 4152 ms and P90 of 8117 ms, about 3300 ms above the telecom median of 852 ms, exceeding the 3000 ms threshold.
- Telecom, Unicom and Mobile medians were 852 ms, 862 ms and 2019 ms respectively, with Mobile relatively higher; observed response IP diversity was 5 addresses.
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.