2a01:8200:4000::/35 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
AS4455 IX Reach Ltd RPKI valid 27 345494455 2026-09-18 2026-09-21
AS31216 BSO Network Solutions SAS RPKI valid 7 14907335631216 2026-09-18 2026-09-21

RPKI

3 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
2a01:8200::/32 /64 AS4455 ripe authorises it
2a01:8200::/32 /64 AS31216 ripe wrong origin
2a01:8200::/32 /48 AS43531 ripe wrong origin

Registry

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

Delegated block
2a01:8200::/32
RIR
RIPENCC
Country
🇫🇷 FR
Status
allocated
Allocated
2011-02-01

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2a01:8200::/32 v6 AS4455 IX Reach Ltd RPKI valid 35 345494455 2026-09-18

More specific routes

2 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
2a01:8200:4400::/48 v6 AS4455 IX Reach Ltd RPKI valid 31 2026-09-18
2a01:8200:4400::/48 v6 AS31216 BSO Network Solutions SAS RPKI valid 3 2026-09-18

Recorded changes

WhenChangeOriginPath
2026-09-18 12:53:53Z origin change AS31216 → AS4455 4439340175358057345494455
2026-09-18 07:11:03Z origin change AS4455 → AS31216 573816939335631216
2026-09-18 06:41:27Z origin change AS31216 → AS4455 494322155104836212994455