38.59.227.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
AS41378 Kirino LLC no ROA 41 24482322341378 2026-10-01 2026-10-25
AS210110 Kvmcloud Network CO., LIMITED no ROA 1 443933571010099210110 2026-10-01 2026-10-25

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
38.0.0.0/8
RIR
ARIN
Country
🇺🇸 US
Status
allocated
Allocated
1991-04-16

Less specific routes

Announced prefixes that contain this one

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.