2606:ae80:1450::/44 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
AS25751 Conversant, Inc. no ROA 17 37721693925751 2026-09-18 2026-09-25
AS26762 Conversant, LLC no ROA 17 38001291426762 2026-09-18 2026-09-25

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
2606:ae80::/32
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
2015-10-23

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-23 22:20:34Z origin change AS25751 β†’ AS26762 2040923401964612676226762
2026-09-23 18:37:03Z origin change AS26762 β†’ AS25751 14907693925751
2026-09-23 18:26:12Z origin change AS25751 β†’ AS26762 2040923401964612676226762
2026-09-23 10:59:11Z origin change AS26762 β†’ AS25751 37721693925751
2026-09-22 08:59:08Z origin change AS25751 β†’ AS26762 348002963264612676226762
2026-09-22 06:22:43Z origin change AS26762 β†’ AS25751 37721693925751
2026-09-20 04:45:22Z origin change AS25751 β†’ AS26762 348002963264612676226762
2026-09-19 08:28:16Z origin change AS26762 β†’ AS25751 29504693925751