54.222.112.0/24 RPKI valid MOAS
Announced by 3 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
| Origin AS | RPKI | Peers seeing it | Sample path | First seen | Last seen |
|---|---|---|---|---|---|
| AS23724 China Telecom Beijing IDC Network | RPKI valid | 19 | 7018413423724 | 2026-09-18 | 2026-09-18 |
| AS9808 China Mobile Backbone | RPKI valid | 18 | 24482584539808 | 2026-09-18 | 2026-09-18 |
| AS55960 Amazon Web Services Beijing (Beijing Sinnet) | RPKI valid | 4 | 3454955114837480855960 | 2026-09-18 | 2026-09-18 |
RPKI
8 ROAs cover this prefix
| ROA prefix | Max length | Authorised origin | Trust anchor | Result for this route |
|---|---|---|---|---|
| 54.222.112.0/24 | /24 | AS4808 | apnic | wrong origin |
| 54.222.112.0/24 | /24 | AS9808 | apnic | wrong origin |
| 54.222.112.0/24 | /24 | AS23724 | apnic | authorises it |
| 54.222.112.0/24 | /24 | AS55960 | apnic | wrong origin |
| 54.222.112.0/23 | /23 | AS4808 | apnic | wrong origin |
| 54.222.112.0/23 | /23 | AS9808 | apnic | wrong origin |
| 54.222.112.0/23 | /23 | AS23724 | apnic | too specific |
| 54.222.112.0/23 | /23 | AS55960 | apnic | wrong origin |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 54.222.0.0/15
- RIR
- APNIC
- Country
- 🇨🇳 CN
- Status
- allocated
- Allocated
- 1992-03-17
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 54.222.112.0/23 v4 | AS9808 China Mobile Backbone | RPKI valid | 18 | 24482584539808 | 2026-09-18 |
| 54.222.112.0/23 v4 | AS23724 China Telecom Beijing IDC Network | RPKI valid | 19 | 7018413423724 | 2026-09-18 |
| 54.222.112.0/23 v4 | AS55960 Amazon Web Services Beijing (Beijing Sinnet) | RPKI valid | 4 | 3454955114837480855960 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.