65.240.184.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
AS203 Level 3 Parent, LLC no ROA 40 377213356203 2026-09-18 2026-09-30
AS22587 Global Payments Inc. no ROA 2 70181349822587 2026-09-18 2026-09-30

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
65.240.0.0/13
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
2002-02-13

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
65.240.0.0/13 v4 AS701 Verizon Business no ROA 41 17639701 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-27 20:32:31Z origin change AS22587 β†’ AS203 85232573356203
2026-09-27 20:30:16Z origin change AS203 β†’ AS22587 1403577701225872258722587
2026-09-23 10:56:44Z origin change AS22587 β†’ AS203 377213356203
2026-09-23 04:45:08Z origin change AS203 β†’ AS22587 7018134981349813498134981349822587
2026-09-18 07:14:22Z origin change AS22587 β†’ AS203 573815030412993356203