139.60.112.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
AS32787 Akamai (Prolexic) no ROA 41 3454932787 2026-09-28 2026-10-17
AS62 CyrusOne LLC no ROA 2 1490762 2026-09-18 2026-10-17

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
139.60.112.0/22
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
2017-10-09

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-10-08 23:20:31Z origin change AS62 β†’ AS32787 5030432787
2026-10-08 22:36:10Z origin change AS32787 β†’ AS62 1490762
2026-10-08 22:35:03Z origin change AS62 β†’ AS32787 701832787
2026-10-08 22:33:57Z origin change AS32787 β†’ AS62 1383097162
2026-10-07 21:35:31Z origin change AS62 β†’ AS32787 5030432787
2026-10-07 19:12:37Z origin change AS32787 β†’ AS62 1490762