162.105.128.0/17 no ROA 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
AS4538 China Education and Research Network Center no ROA 41 244824538 2026-09-18 2026-09-18
AS24349 CERNET2 IX at Peking University no ROA 1 3822923855766023911453824349 2026-09-18 2026-09-18

RPKI

No ROA covers this prefix

No ROA covers this prefix, so origin validation returns "unknown". That is not a fault; most of the table is still unsigned.

Registry

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

Delegated block
162.105.0.0/16
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
1992-09-30

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
162.105.0.0/16 v4 AS4538 China Education and Research Network Center no ROA 47 244824538 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 08:32:48Z origin change AS24349 → AS4538 333311032096545384538
2026-09-18 08:32:20Z origin change AS4538 → AS24349 333311032096523911453824349
2026-09-18 08:31:25Z origin change AS24349 → AS4538 3333125717445384538453845384538
2026-09-18 08:29:35Z origin change AS4538 → AS24349 333311032096523911453824349
2026-09-18 07:13:55Z origin change AS24349 → AS4538 3333125717445384538453845384538