2c0f:f428:8000::/33 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
AS30844 Liquid Intelligent Technologies no ROA 4 566622509130844 2026-10-22 2026-10-30
AS64613 no ROA 2 380013084464613 2026-10-22 2026-10-30

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
2c0f:f428::/32
RIR
AFRINIC
Country
🇹🇿 TZ
Status
allocated
Allocated
2015-04-22

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2c0f:f428::/32 v6 AS30844 Liquid Intelligent Technologies no ROA 33 3800130844 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-29 13:39:42Z origin change AS64613 → AS30844 566622509130844
2026-10-27 16:45:02Z origin change AS30844 → AS64613 380013084464613
2026-10-22 01:48:15Z origin change AS64613 → AS30844 204092340192509130844
2026-10-22 01:48:12Z origin change AS30844 → AS64613 380013084464613
2026-10-22 01:48:10Z origin change AS64613 → AS30844 573814270830844
2026-10-22 01:48:07Z origin change AS30844 → AS64613 503043084464613