198.218.26.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
AS27137 United States Department of Defense (DoD) no ROA 43 3772133567212706627137 2026-10-14 2026-10-14
AS27138 United States Department of Defense (DoD) no ROA 1 21324190023356721270662713727138 2026-09-18 2026-10-14

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
198.218.0.0/16
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
1993-07-09

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
198.218.0.0/15 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-13 20:43:28Z origin change AS27138 β†’ AS27137 140357733567217212706627137
2026-10-13 20:43:27Z origin change AS27137 β†’ AS27138 46081221463733567217212706627137271382713827138
2026-10-13 20:43:25Z origin change AS27138 β†’ AS27137 17639693933567217212706627137