120.92.40.0/21 RPKI valid MOAS
Announced by 2 different origins, which is either a deliberate multi-origin setup or a hijack.
This prefix is announced by more than one AS. Compare how many collector
peers see each origin below: a hijack is usually visible as a second
origin seen by far fewer peers than the legitimate one.
Origins
RPKI
6 ROAs cover this prefix
| ROA prefix | Max length | Authorised origin | Trust anchor | Result for this route |
|---|---|---|---|---|
| 120.92.40.0/21 | /21 | AS23724 | apnic | wrong origin |
| 120.92.40.0/21 | /21 | AS59019 | apnic | authorises it |
| 120.92.40.0/21 | /21 | AS133119 | apnic | wrong origin |
| 120.92.40.0/21 | /21 | AS137280 | apnic | wrong origin |
| 120.92.0.0/17 | /17 | AS23724 | apnic | wrong origin |
| 120.92.0.0/17 | /17 | AS59019 | apnic | too specific |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 120.92.0.0/16
- RIR
- APNIC
- Country
- 🇨🇳 CN
- Status
- allocated
- Allocated
- 2008-04-01
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 120.92.0.0/17 v4 | AS59019 Beijing Kingsoft Cloud Internet Technology Co., Ltd | RPKI valid | 7 | 34549551148371762159019 | 2026-09-18 |
| 120.92.0.0/17 v4 | AS23724 China Telecom Beijing IDC Network | RPKI valid | 34 | 7018413423724 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.