177.2.20.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
AS400618 Prime Security Corp. RPKI valid 41 244829886140096400618 2026-09-18 2026-09-20
AS8796 FASTNET DATA INC RPKI valid 1 4439335710100998796 2026-09-18 2026-09-20

RPKI

5 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
177.2.20.0/22 /24 AS400618 apnic authorises it
177.2.16.0/20 /24 AS8796 apnic wrong origin
177.2.16.0/20 /24 AS40115 apnic wrong origin
177.2.16.0/20 /24 AS140227 apnic wrong origin
177.2.16.0/20 /24 AS395886 apnic wrong origin

Registry

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

Delegated block
177.2.16.0/20
RIR
APNIC
Country
🇭🇰 HK
Status
allocated
Allocated
2025-03-13

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

6 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
177.2.20.0/23 v4 AS400618 Prime Security Corp. RPKI valid 38 2026-09-18
177.2.20.0/24 v4 AS400618 Prime Security Corp. RPKI valid 19 2026-09-18
177.2.21.0/24 v4 AS400618 Prime Security Corp. RPKI valid 19 2026-09-18
177.2.22.0/23 v4 AS400618 Prime Security Corp. RPKI valid 38 2026-09-18
177.2.22.0/24 v4 AS400618 Prime Security Corp. RPKI valid 19 2026-09-18
177.2.23.0/24 v4 AS400618 Prime Security Corp. RPKI valid 19 2026-09-18