2a0d:59c7::/32 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
AS8903 LYNTIA NETWORKS S.A. RPKI valid 36 345498903 2026-09-18 2026-09-24
AS12541 LYNTIA NETWORKS S.A. RPKI valid 1 3333332012541 2026-09-18 2026-09-24

RPKI

5 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
2a0d:59c7::/32 /32 AS8903 ripe authorises it
2a0d:59c7::/32 /32 AS202766 ripe wrong origin
2a0d:59c0::/29 /48 AS8903 ripe authorises it
2a0d:59c0::/29 /48 AS12541 ripe wrong origin
2a0d:59c0::/29 /48 AS202766 ripe wrong origin

Registry

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

Delegated block
2a0d:59c0::/29
RIR
RIPENCC
Country
🇪🇸 ES
Status
allocated
Allocated
2018-09-07

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2a0d:59c0::/29 v6 AS12541 LYNTIA NETWORKS S.A. RPKI valid 1 3333332012541 2026-09-18
2a0d:59c0::/29 v6 AS8903 LYNTIA NETWORKS S.A. RPKI valid 36 345498903 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 04:39:44Z origin change AS12541 → AS8903 20236569398903
2026-09-18 04:29:41Z origin change AS12541 → AS8903 20236569398903
2026-09-18 04:20:42Z origin change AS12541 → AS8903 20236569398903
2026-09-18 04:08:29Z origin change AS12541 → AS8903 20236569398903