205.180.85.0/24 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
AS26762 Conversant, LLC no ROA 34 34549646126762 2026-09-18 2026-09-22
AS25751 Conversant, Inc. no ROA 9 3772125751 2026-09-18 2026-09-22

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
205.180.0.0/14
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
1995-03-21

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
205.180.0.0/14 v4 AS3356 Lumen (Level 3) no ROA 43 377213356 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-22 11:37:25Z origin change AS25751 β†’ AS26762 852646164612676226762
2026-09-22 11:30:14Z origin change AS26762 β†’ AS25751 55720693925751
2026-09-22 06:20:32Z origin change AS25751 β†’ AS26762 32884032772717433562676226762
2026-09-22 06:20:25Z origin change AS26762 β†’ AS25751 3772125751