23.129.76.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
AS135663 BengalHost no ROA 42 34549137409932136826135663 2026-09-18 2026-09-27
AS13875 MxFiber LLC no ROA 1 44393357101009913875 2026-09-18 2026-09-27

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

No delegation record covers this prefix.

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

1 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
23.129.76.0/24 v4 AS13378 Qingye Cloud RPKI valid 3 2026-09-18