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

Origin ASRPKI Peers seeing itSample path First seenLast seen
AS4812 China Telecom Shanghai Province Network RPKI valid 31 701841344812 2026-09-18 2026-09-18
AS17621 China Unicom Shanghai network RPKI valid 10 345495511483717621 2026-09-18 2026-09-18

RPKI

3 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
120.136.184.0/22 /24 AS4812 apnic authorises it
120.136.184.0/22 /24 AS17621 apnic wrong origin
120.136.184.0/22 /24 AS23853 apnic wrong origin

Registry

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

Delegated block
120.136.128.0/18
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2008-04-08

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
120.136.184.0/23 v4 AS17621 China Unicom Shanghai network RPKI valid 41 345495511483717621 2026-09-18
120.136.184.0/22 v4 AS23853 Shanghai Data Solution Co., Ltd. RPKI valid 3 4439335710100999929483798082440023853 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 06:49:02Z origin change AS17621 → AS4812 557202376441344812
2026-09-18 06:29:50Z origin change AS4812 → AS17621 3492756655483717621
2026-09-18 04:41:33Z origin change AS17621 → AS4812 557209930291441344812
2026-09-18 04:36:57Z origin change AS17621 → AS4812 557202376441344812
2026-09-18 04:16:58Z origin change AS17621 → AS4812 557202376441344812