103.217.163.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
AS41095 IPTP LTD RPKI valid 43 85241095 2026-09-18 2026-11-03
AS140951 IPTP Networks RPKI valid 1 2448210135140951 2026-09-18 2026-11-03

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
103.217.163.0/24 /24 AS41095 apnic authorises it
103.217.163.0/24 /24 AS140951 apnic wrong origin
103.217.162.0/23 /23 AS140951 apnic wrong origin
103.217.160.0/22 /22 AS41095 apnic too specific

Registry

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

Delegated block
103.217.160.0/22
RIR
APNIC
Country
🇭🇰 HK
Status
assigned
Allocated
2016-05-09

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-24 14:02:06Z origin change AS140951 → AS41095 580571836335641095
2026-10-23 20:03:41Z origin change AS41095 → AS140951 2448210135140951