101.251.248.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
AS23724 China Telecom Beijing IDC Network RPKI valid 2 4439335710100999929413423724 2026-09-18 2026-10-16
AS56048 China Mobile Group Beijing Company RPKI valid 1 557201747658453980856048 2026-09-18 2026-10-16

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
101.251.248.0/22 /22 AS23724 apnic authorises it
101.251.248.0/22 /22 AS56048 apnic wrong origin
101.251.240.0/20 /20 AS23724 apnic too specific
101.251.224.0/19 /19 AS23724 apnic too specific

Registry

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

Delegated block
101.251.128.0/17
RIR
APNIC
Country
🇨🇳 CN
Status
allocated
Allocated
2011-03-09

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
101.251.240.0/20 v4 AS23724 China Telecom Beijing IDC Network RPKI valid 42 7018413423724 2026-09-18
101.251.224.0/19 v4 AS23724 China Telecom Beijing IDC Network RPKI valid 42 7018413423724 2026-09-18

More specific routes

6 announced prefixes inside this one

Recorded changes

WhenChangeOriginPath
2026-10-14 18:07:09Z origin change AS23724 → AS56048 557201747658453980856048
2026-10-14 03:32:12Z origin change AS56048 → AS23724 3798956300132132100994837413423724
2026-10-12 10:54:31Z origin change AS23724 → AS56048 20409220766291693528089661580258453980856048
2026-10-07 16:09:07Z origin change AS56048 → AS23724 3798956300132132100994837413423724