110.43.176.0/21 RPKI valid 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
AS23724 China Telecom Beijing IDC Network RPKI valid 30 7018413423724 2026-09-18 2026-09-18
AS133119 China Unicom IP network RPKI valid 11 3454955114837133119 2026-09-18 2026-09-18

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
110.43.176.0/21 /21 AS23724 apnic authorises it
110.43.176.0/21 /21 AS59019 apnic wrong origin
110.43.176.0/21 /21 AS133119 apnic wrong origin
110.43.0.0/16 /16 AS59019 apnic wrong origin

Registry

Who this address space is delegated to, regardless of whether it is routed

Delegated block
110.40.0.0/14
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2009-03-04

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
110.43.0.0/16 v4 AS59019 Beijing Kingsoft Cloud Internet Technology Co., Ltd RPKI valid 42 701841345854259019 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 07:14:21Z origin change AS133119 → AS23724 5738142708413423724
2026-09-18 05:28:20Z origin change AS23724 → AS133119 49673204854837133119
2026-09-18 05:28:05Z origin change AS133119 → AS23724 4967320485413423724