101.251.240.0/24 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 |
|---|---|---|---|---|
| 101.251.240.0/24 | /24 | AS23724 | apnic | wrong origin |
| 101.251.240.0/24 | /24 | AS56048 | apnic | authorises it |
| 101.251.240.0/21 | /21 | AS23724 | apnic | wrong origin |
| 101.251.240.0/21 | /21 | AS56048 | apnic | too specific |
| 101.251.240.0/20 | /20 | AS23724 | apnic | wrong origin |
| 101.251.224.0/19 | /19 | AS23724 | apnic | wrong origin |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 101.251.128.0/17
- RIR
- APNIC
- Country
- 🇨🇳 CN
- Status
- allocated
- Allocated
- 2011-03-09
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 101.251.240.0/21 v4 | AS23724 China Telecom Beijing IDC Network | RPKI valid | 1 | 4439335710100999929413423724 | 2026-09-18 |
| 101.251.240.0/21 v4 | AS56048 China Mobile Group Beijing Company | RPKI valid | 2 | 557201747658453980856048 | 2026-09-18 |
| 101.251.240.0/20 v4 | AS23724 China Telecom Beijing IDC Network | RPKI valid | 41 | 7018413423724 | 2026-09-18 |
| 101.251.224.0/19 v4 | AS23724 China Telecom Beijing IDC Network | RPKI valid | 41 | 7018413423724 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.