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 m.867news.cc
- Tested
- Sep 26, 2026, 3:18 PM
- Completed probes
- 12/12
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- --
This HTTP website speed test of m.867news.cc on 2026-09-20 covered 317 nodes with a 99.7% response rate and a median total response time of 1044 ms. It observed higher overseas latency and 11 HTTP 502 status codes, which warrant further ver
There is not enough network HTTP speed-test data to draw this chart.
Key findings
- The overall response rate was 99.7%: 316 nodes returned a valid HTTP response, 1 node did not obtain a valid result, and 11 HTTP 502 status codes were recorded.
- Median total response time was 1044 ms, with p90 at 3435 ms and p95 at 5857 ms, showing wide variation across nodes.
- Overseas nodes showed a median total response time of 4238 ms, 3451 ms above telecom's 787 ms and beyond the 3000 ms threshold.
- Mobile nodes showed a median of 2587 ms, higher than telecom and unicom; unicom recorded 1047 ms with a 100% response rate.
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.