119.254.0.0/20 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 40 7018413423724 2026-09-18 2026-10-04
AS4808 China Unicom Beijing Province Network RPKI valid 1 557201009948374808 2026-09-18 2026-10-04

RPKI

5 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
119.254.0.0/20 /20 AS4808 apnic wrong origin
119.254.0.0/20 /20 AS23724 apnic authorises it
119.254.0.0/17 /17 AS23724 apnic too specific
119.254.0.0/17 /17 AS23844 apnic wrong origin
119.254.0.0/16 /16 AS23844 apnic wrong origin

Registry

Who this address space is delegated to, regardless of whether it is routed

Delegated block
119.254.0.0/15
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2008-03-13

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
119.254.0.0/17 v4 AS23724 China Telecom Beijing IDC Network RPKI valid 41 7018413423724 2026-09-18
119.254.0.0/16 v4 AS23844 Beijing Guanghuan Xinwang Digital RPKI valid 42 345496453140591992913779423844 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-02 03:28:40Z origin change AS4808 → AS23724 557206939413423724
2026-10-02 03:28:35Z origin change AS23724 → AS4808 557201009948374808