41.174.136.0/21 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 39 5030430844 2026-09-18 2026-09-19
AS65510 no ROA 2 380013084465510 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
41.160.0.0/12
RIR
AFRINIC
Country
🇲🇺 MU
Status
allocated
Allocated
2007-02-22

Less specific routes

Announced prefixes that contain this one

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-19 06:27:29Z origin change AS65510 → AS30844 14907335617430844
2026-09-19 06:27:22Z origin change AS30844 → AS65510 244823084465510
2026-09-19 06:26:50Z origin change AS65510 → AS30844 599199002335617430844
2026-09-19 06:26:48Z origin change AS30844 → AS65510 380013084465510
2026-09-19 06:26:25Z origin change AS65510 → AS30844 204092340192509130844
2026-09-19 06:26:22Z origin change AS65510 → AS30844 2950415935495591583030844
2026-09-19 06:26:22Z origin change AS30844 → AS65510 333311033084465510
2026-09-19 06:26:22Z origin change AS30844 → AS65510 333311033084465510
2026-09-18 07:14:24Z origin change AS65510 → AS30844 573815030430844