74.209.244.0/23 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
AS13767 DataBank Holdings, Ltd. no ROA 25 22652129913767 2026-09-18 2026-09-19
AS29944 Latisys-Ashburn, LLC no ROA 17 34549646129944 2026-09-18 2026-09-19

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
74.209.192.0/18
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
2008-03-24

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
74.209.192.0/18 v4 AS13767 DataBank Holdings, Ltd. no ROA 25 22652129913767 2026-09-18
74.209.192.0/18 v4 AS29944 Latisys-Ashburn, LLC no ROA 17 34549646129944 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-19 18:42:17Z origin change AS29944 β†’ AS13767 328840327727174335613767
2026-09-19 17:02:08Z origin change AS13767 β†’ AS29944 44393580576939646129944
2026-09-19 08:43:57Z origin change AS29944 β†’ AS13767 328840327727174335613767
2026-09-19 08:30:30Z origin change AS13767 β†’ AS29944 2950415935646129944
2026-09-18 14:03:00Z origin change AS29944 β†’ AS13767 328840327727174335613767