185.72.76.0/22 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
AS196983 Elsynet S.r.l. no ROA 42 24482196983 2026-09-18 2026-10-01
AS59777 EGEA ENTE GESTIONE ENERGIA AMBIENTE SPA no ROA 1 21628582806762326959777 2026-09-18 2026-10-01

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
185.72.76.0/22
RIR
RIPENCC
Country
🇮🇹 IT
Status
allocated
Allocated
2014-10-06

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-30 22:44:48Z origin change AS59777 → AS196983 2023655067312779196983
2026-09-30 22:44:25Z origin change AS196983 → AS59777 202365506736762326959777
2026-09-25 13:04:06Z origin change AS59777 → AS196983 852325712779196983
2026-09-25 10:59:33Z origin change AS196983 → AS59777 21628582806762326959777
2026-09-21 22:39:53Z origin change AS59777 → AS196983 496731238912779196983
2026-09-21 22:14:39Z origin change AS196983 → AS59777 21628582806762326959777