120.92.200.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

Origin ASRPKI Peers seeing itSample path First seenLast seen
AS23724 China Telecom Beijing IDC Network RPKI valid 41 7018413423724 2026-09-18 2026-10-10
AS133119 China Unicom IP network RPKI valid 1 3798956300132132100994837133119 2026-10-08 2026-10-10

RPKI

7 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
120.92.200.0/21 /21 AS23724 apnic authorises it
120.92.200.0/21 /21 AS59019 apnic wrong origin
120.92.200.0/21 /21 AS133119 apnic wrong origin
120.92.200.0/21 /21 AS137280 apnic wrong origin
120.92.192.0/19 /19 AS23724 apnic too specific
120.92.192.0/19 /19 AS59019 apnic wrong origin
120.92.192.0/19 /19 AS133119 apnic wrong origin

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.192.0/19 v4 AS23724 China Telecom Beijing IDC Network RPKI valid 41 7018413423724 2026-09-18
120.92.192.0/19 v4 AS133119 China Unicom IP network RPKI valid 1 3798956300132132100994837133119 2026-10-08

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-09 04:04:24Z origin change AS59019 → AS23724 557202914413423724
2026-10-09 03:30:33Z origin change AS23724 → AS59019 557201747658453980859019
2026-10-07 16:19:01Z origin change AS133119 → AS23724 149071299413423724
2026-10-07 16:09:07Z origin change AS23724 → AS133119 3798956300132132100994837133119