199.252.155.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
AS721 United States Department of Defense (DoD) no ROA 43 377213356721 2026-09-18 2026-10-11
AS5927 United States Department of Defense (DoD) no ROA 1 379895630013213246573356721270665927 2026-10-08 2026-10-11

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
199.252.0.0/16
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
1994-05-02

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
199.252.128.0/18 v4 AS721 United States Department of Defense (DoD) no ROA 44 377213356721 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-07 16:20:11Z origin change AS5927 β†’ AS721 1490712993356721721
2026-10-07 16:09:10Z origin change AS721 β†’ AS5927 379895630013213246573356721721270665927