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 156.238.122.133
- Tested
- Sep 17, 2026, 11:20 AM
- Completed probes
- 12/12
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- --
This HTTP website speed test ran on 2026-09-17 against 156.238.122.133. Of 307 observed nodes, none obtained a valid HTTP response, giving a 0% response rate, and no total response time data was recorded.
There is not enough network HTTP speed-test data to draw this chart.
Key findings
- All 307 observed nodes failed to return a valid HTTP response, a 0% response rate below the 95% threshold.
- Telecom, Unicom, Mobile, and overseas carriers each showed a 0% response rate with no HTTP 2xx status codes recorded.
- The 12 platform probe failures are excluded from observed node counts and are not attributed to the tested website.
- No total response time data was obtained, so p50, p90, p95, and average values are unavailable.
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.