2a02:2188::/48 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
AS48469 mnemonic AS RPKI valid 23 37721335648469 2026-09-18 2026-09-21
AS60848 mnemonic AS RPKI valid 12 50304211660848 2026-09-18 2026-09-21

RPKI

2 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
2a02:2188::/48 /48 AS48469 ripe authorises it
2a02:2188::/48 /48 AS60848 ripe wrong origin

Registry

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

Delegated block
2a02:2188::/32
RIR
RIPENCC
Country
🇳🇴 NO
Status
allocated
Allocated
2010-07-16

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-09-21 17:29:01Z origin change AS48469 → AS60848 3454912552211660848
2026-09-21 13:29:16Z origin change AS60848 → AS48469 21628582806762335648469
2026-09-21 05:32:37Z origin change AS48469 → AS60848 494322155104836212552211660848
2026-09-21 05:08:24Z origin change AS60848 → AS48469 21628582806762335648469
2026-09-19 20:03:16Z origin change AS48469 → AS60848 2448212552211660848
2026-09-19 08:28:12Z origin change AS60848 → AS48469 2950415935174335648469