2001:67c:1254::/48 no ROA 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 no ROA 33 345494455 2026-09-18 2026-10-03
AS31216 BSO Network Solutions SAS no ROA 1 21628582806762335631216 2026-09-22 2026-10-03

RPKI

No ROA covers this prefix

No ROA covers this prefix, so origin validation returns "unknown". That is not a fault; most of the table is still unsigned.

Registry

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

Delegated block
2001:67c:1254::/48
RIR
RIPENCC
Country
🇫🇷 FR
Status
assigned
Allocated
2012-08-27

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2000::/6 v6 AS29632 Netassist International EOOD no ROA 1 6121829632 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-22 10:50:35Z origin change AS31216 → AS4455 34927566554455
2026-09-22 09:14:02Z origin change AS4455 → AS31216 21628582806762335631216
2026-09-21 11:10:25Z origin change AS31216 → AS4455 503004455
2026-09-21 11:02:12Z origin change AS4455 → AS31216 50300335631216