Nationwide Speed Map
- >10s
- 3s-10s
- 1s-3s
- 0.5s-1s
- <=0.5s
11 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: 11/11
| 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 | -- | -- | -- | -- | -- | -- |
Website Speed Test Test Findings for 2231olhfhiwek09.2231sjnfnjiwge34fl.website
- Tested
- Sep 28, 2026, 7:24 PM
- Completed probes
- 11/11
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- --
This HTTP website speed test ran on 2026-09-28. The overall response rate was 92.1%, below the 95% threshold, with a median total response time of 355 ms and a P90 of 763 ms. All valid responses returned HTTP 200.
There is not enough network HTTP speed-test data to draw this chart.
Key findings
- The overall response rate was 92.1%, below the 95% threshold: 291 of 317 expected nodes returned a valid HTTP response, while 25 did not.
- The mobile carrier response rate was 88.5%, 11.5 percentage points below the overseas carrier's 100%, exceeding the 10-point threshold.
- The overseas carrier showed a median total response time of 638 ms and a P90 of 1265 ms, well above the 339 ms median seen on telecom and unicom.
- Valid responses came from 8 distinct response IPs, all with HTTP status code 200; no other status codes appeared.
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.