192.96.139.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
AS37315 Cipherwave no ROA 40 503043766237315 2026-09-18 2026-11-01
AS64512 Private ASN no ROA 2 38001308443731564512 2026-09-18 2026-11-01

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
192.96.139.0/24
RIR
AFRINIC
Country
πŸ‡ΏπŸ‡¦ ZA
Status
assigned
Allocated
1993-03-30

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-24 14:02:10Z origin change AS64512 β†’ AS37315 5805717430844373153731537315
2026-10-23 20:09:12Z origin change AS37315 β†’ AS64512 244823084437315373153731564512
2026-10-20 10:02:19Z origin change AS64512 β†’ AS37315 32884032772717430844373153731537315
2026-10-20 09:54:19Z origin change AS37315 β†’ AS64512 333311033084437315373153731564512