suzhou-SUZHOU-YAXUDIANZIKEJI

BGP inherited
Cluster stats
Netblocks8
All fragments 1,221 blocks across 988 clusters
Cluster ID211901310
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
58.210.217.0/29 suzhou-SUZHOU-YAXUDIANZIKEJI APNIC ASSIGNED NON-PORTABLE ● low
58.210.217.8/29 suzhou-SUZHOU-YAXUDIANZIKEJI APNIC ASSIGNED NON-PORTABLE ● low
222.92.217.72/30 suzhou-SUZHOU-YAXUDIANZIKEJI APNIC ASSIGNED NON-PORTABLE ● low
222.92.217.76/30 suzhou-SUZHOU-YAXUDIANZIKEJI APNIC ASSIGNED NON-PORTABLE ● low
222.92.217.84/30 suzhou-SUZHOU-YAXUDIANZIKEJI APNIC ASSIGNED NON-PORTABLE ● low
222.92.217.88/30 suzhou-SUZHOU-YAXUDIANZIKEJI-CORP APNIC ASSIGNED NON-PORTABLE ● low
222.92.219.232/29 suzhou-SUZHOU-YAXUDIANZIKEJI APNIC ASSIGNED NON-PORTABLE ● low
222.92.219.240/28 suzhou-SUZHOU-YAXUDIANZIKEJI APNIC ASSIGNED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

CH446-AP CH446-AP MAINT-CHINANET-JS