139.198.121.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
AS134366 Cloud Computing HK Limited RPKI valid 40 24482134366 2026-09-18 2026-10-22
AS58466 CHINANET Guangdong province network RPKI valid 1 3798956300132132100994837413458466 2026-10-08 2026-10-22

RPKI

6 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
139.198.121.0/24 /24 AS58466 apnic wrong origin
139.198.121.0/24 /24 AS59078 apnic wrong origin
139.198.121.0/24 /24 AS134366 apnic authorises it
139.198.120.0/21 /21 AS58466 apnic wrong origin
139.198.0.0/17 /17 AS59078 apnic wrong origin
139.198.0.0/16 /16 AS59078 apnic wrong origin

Registry

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

Delegated block
139.196.0.0/14
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2011-03-09

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
139.198.120.0/21 v4 AS58466 CHINANET Guangdong province network RPKI valid 2 4439335710100999929413458466 2026-09-18
139.198.0.0/16 v4 AS59078 Yunify Technologies Inc. RPKI valid 44 345491745845398082440059078 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-14 03:35:00Z origin change AS58466 → AS134366 3288403277271743491134366134366134366
2026-10-14 03:32:14Z origin change AS134366 → AS58466 3798956300132132100994837413458466