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 | 上海数据中心 0.3511s | 河北电信 0.5704s | 0.461s |
| China Telecom | 河北电信 0.5704s | 河北电信 0.5704s | 0.570s |
| China Unicom | 上海数据中心 0.3511s | 上海数据中心 0.3511s | 0.351s |
| China Mobile | -- | -- | -- |
| East China | 上海数据中心 0.3511s | 上海数据中心 0.3511s | 0.351s |
| South China | -- | -- | -- |
| Central China | -- | -- | -- |
| North China | 河北电信 0.5704s | 河北电信 0.5704s | 0.570s |
| Southwest | -- | -- | -- |
| Northwest | -- | -- | -- |
| Northeast | -- | -- | -- |
| HK/MO/TW | -- | -- | -- |
DNS Resolution Stats
2Showing: 12/12
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| 电信贵州贵阳电信 | -- | Failed | -- | -- | |||||
| 电信湖北十堰电信 | -- | Failed | -- | -- | |||||
| 电信深圳电信 | -- | Failed | -- | -- | |||||
| 电信苏州电信 | -- | Failed | -- | -- | |||||
| 电信四川广安电信 | -- | Failed | -- | -- | |||||
| 电信河北电信 | 103.48.7.35 | 中国/香港/戴讯互联有限公司 | 200 | 0.5704s | 0.1391s | 0.313s | 0.1153s | -- | |
| 电信北京电信 | -- | Failed | -- | -- | |||||
| 联通甘肃联通 | -- | Failed | -- | -- | |||||
| 联通上海数据中心 | 69.160.175.208 | 中国/香港/戴讯互联有限公司 | 200 | 0.3511s | 0.0615s | 0.2196s | 0.0673s | -- | |
| 海外俄罗斯莫斯科 | -- | Failed | -- | -- | |||||
| 海外柬埔寨金边 | -- | Failed | -- | -- | |||||
| 海外迪拜 | -- | Failed | -- | -- |
Website Speed Test Test Findings for 2652.app
- Tested
- Aug 24, 2026, 1:29 AM
- Completed probes
- 12/12
- Valid HTTP response probes
- 2 (16.7%)
- Average total response time
- 461 ms
2652.app 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 (%)
50%Highest rate
P50 total response time
Total response time (ms)
351 msLowest P50
Improvement recommendations
- The HTTP response rate is 16.7%, 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.