111.235.173.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
AS58536 CONAC (China Organizational Name Administration Center) no ROA 39 70184837480858536 2026-09-18 2026-10-24
AS58811 CONAC (China Organizational Name Administration Center) no ROA 4 3800174735845398085604858811 2026-09-18 2026-10-24

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
111.235.160.0/19
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2009-08-18

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-23 19:18:11Z origin change AS58811 → AS58536 226521744134481258536
2026-10-23 09:21:51Z origin change AS58536 → AS58811 5782112586325758453584535845398085604858811
2026-10-23 00:01:38Z origin change AS58811 → AS58536 57381427084134481258536
2026-10-22 22:10:32Z origin change AS58536 → AS58811 5738142708129958453584535845398085604858811
2026-10-22 03:20:23Z origin change AS58811 → AS58536 1763934914134481258536
2026-10-22 02:17:17Z origin change AS58536 → AS58811 5782112586325758453584535845398085604858811
2026-10-14 23:24:30Z origin change AS58811 → AS58536 1763934914134481258536
2026-10-14 18:07:04Z origin change AS58536 → AS58811 5572029145845398085604858811