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.059s | 苏州电信 0.059s | 0.059s |
| China Telecom | 苏州电信 0.059s | 苏州电信 0.059s | 0.059s |
| China Unicom | -- | -- | -- |
| China Mobile | -- | -- | -- |
| East China | 苏州电信 0.059s | 苏州电信 0.059s | 0.059s |
| South China | -- | -- | -- |
| Central China | -- | -- | -- |
| North China | -- | -- | -- |
| Southwest | -- | -- | -- |
| Northwest | -- | -- | -- |
| Northeast | -- | -- | -- |
| HK/MO/TW | -- | -- | -- |
DNS Resolution Stats
1Showing: 12/12
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| 电信贵州贵阳电信 | -- | Failed | -- | -- | |||||
| 电信湖北十堰电信 | -- | Failed | -- | -- | |||||
| 电信深圳电信 | -- | Failed | -- | -- | |||||
| 电信苏州电信 | 180.109.0.221 | 中国/江苏/南京市/电信 | 200 | 0.059s | 0.003s | 0.0318s | 0.0231s | -- | |
| 电信四川广安电信 | -- | Failed | -- | -- | |||||
| 电信河北电信 | -- | Failed | -- | -- | |||||
| 电信北京电信 | -- | Failed | -- | -- | |||||
| 联通甘肃联通 | -- | Failed | -- | -- | |||||
| 联通上海数据中心 | -- | Failed | -- | -- | |||||
| 海外俄罗斯莫斯科 | -- | Failed | -- | -- | |||||
| 海外柬埔寨金边 | -- | Failed | -- | -- | |||||
| 海外迪拜 | -- | Failed | -- | -- |
Website Speed Test Test Findings for sequoia-gate.myyixi.com
- Tested
- Aug 24, 2026, 1:26 AM
- Completed probes
- 12/12
- Valid HTTP response probes
- 1 (8.3%)
- Average total response time
- 59 ms
sequoia-gate.myyixi.com 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 (%)
14.3%Highest rate
P50 total response time
Total response time (ms)
59 msLowest P50
Improvement recommendations
- The HTTP response rate is 8.3%, 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.