175.25.16.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 29 37721174413423724 2026-09-18 2026-09-18
AS4808 China Unicom Beijing Province Network RPKI valid 13 701848374808 2026-09-18 2026-09-18

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
175.25.16.0/21 /21 AS4808 apnic wrong origin
175.25.16.0/21 /21 AS23724 apnic authorises it
175.25.16.0/21 /21 AS56019 apnic wrong origin
175.25.0.0/16 /16 AS56019 apnic wrong origin

Registry

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

Delegated block
175.25.0.0/16
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2009-12-04

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
175.25.0.0/16 v4 AS56019 Beijing ShuJuJia Technology Co., Ltd. RPKI valid 42 701841342372456019 2026-09-18

More specific routes

4 announced prefixes inside this one

Recorded changes

WhenChangeOriginPath
2026-09-18 06:49:02Z origin change AS4808 → AS23724 5572023764413423724
2026-09-18 06:29:50Z origin change AS23724 → AS4808 349275665548374808