2001:67c:1874::/48 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
AS29632 Netassist International EOOD no ROA 19 3480029632 2026-09-18 2026-09-19
AS8772 NetAssist LLC no ROA 16 33338772 2026-09-18 2026-09-19

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
2001:67c:1874::/48
RIR
RIPENCC
Country
🇧🇬 BG
Status
assigned
Allocated
2013-10-21

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2000::/6 v6 AS29632 Netassist International EOOD no ROA 1 6121829632 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-19 06:42:01Z origin change AS8772 → AS29632 3492734927693929632
2026-09-19 02:25:18Z origin change AS29632 → AS8772 494322155105811590028772
2026-09-18 07:10:58Z origin change AS8772 → AS29632 57381693929632
2026-09-18 06:41:22Z origin change AS29632 → AS8772 494322155105811590028772