103.252.36.0/22 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
AS56048 China Mobile Group Beijing Company RPKI valid 2 557201747658453980856048 2026-09-18 2026-09-18
AS23724 China Telecom Beijing IDC Network RPKI valid 1 4439335710100999929413423724 2026-09-18 2026-09-18

RPKI

2 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
103.252.36.0/22 /22 AS23724 apnic wrong origin
103.252.36.0/22 /22 AS56048 apnic authorises it

Registry

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

Delegated block
103.252.36.0/22
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2013-10-22

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

1 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
103.252.36.0/24 v4 AS4808 China Unicom Beijing Province Network RPKI valid 42 2026-09-18