2401:47c0:1f00::/40 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 33 85241095 2026-09-18 2026-09-23
AS140951 IPTP Networks RPKI valid 2 1763963927140951 2026-09-18 2026-09-23

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
2401:47c0:1f00::/40 /40 AS41095 apnic authorises it
2401:47c0:1f00::/40 /40 AS140951 apnic wrong origin
2401:47c0:1000::/36 /36 AS41095 apnic too specific
2401:47c0::/32 /32 AS41095 apnic too specific

Registry

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

Delegated block
2401:47c0::/32
RIR
APNIC
Country
🇭🇰 HK
Status
allocated
Allocated
2017-06-07

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2401:47c0:1000::/36 v6 AS41095 IPTP LTD RPKI valid 35 2448241095 2026-09-18
2401:47c0::/32 v6 AS41095 IPTP LTD RPKI valid 35 2448241095 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 05:35:26Z origin change AS140951 → AS41095 49432483629002335641095