139.198.108.0/22 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
AS58466 CHINANET Guangdong province network RPKI valid 2 4439335710100999929413458466 2026-09-18 2026-10-26
AS59078 Yunify Technologies Inc. RPKI valid 1 55720174765845398085604059078 2026-09-18 2026-10-26

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
139.198.108.0/22 /22 AS58466 apnic authorises it
139.198.108.0/22 /22 AS59078 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.0.0/16 v4 AS59078 Yunify Technologies Inc. RPKI valid 44 345491745845398082440059078 2026-09-18

More specific routes

2 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
139.198.108.0/24 v4 AS59078 Yunify Technologies Inc. RPKI valid 1 2026-09-18
139.198.109.0/24 v4 AS59078 Yunify Technologies Inc. RPKI valid 1 2026-09-18

Recorded changes

WhenChangeOriginPath
2026-10-14 18:07:01Z origin change AS58466 → AS59078 55720174765845398085604059078
2026-10-14 03:32:14Z origin change AS59078 → AS58466 3798956300132132100994837413458466