No.31, Jin-rong Street

SUZHOU-TELECOM-CLIENT-CENTRE
BGP inherited
Cluster stats
Netblocks6
All fragments 16 blocks across 3 clusters
Cluster ID206594569
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
58.211.190.8/29 SUZHOU-TELECOM-CLIENT-CENTRE APNIC ASSIGNED NON-PORTABLE ● high
58.211.190.144/29 SUZHOU-TELECOM-CLIENT-CENTRE APNIC ASSIGNED NON-PORTABLE ● high
58.211.251.40/29 SUZHOU-TELECOM-CLIENT-CENTRE APNIC ASSIGNED NON-PORTABLE ● high
58.211.251.48/29 SUZHOU-TELECOM-CLIENT-CENTRE APNIC ASSIGNED NON-PORTABLE ● high
58.211.251.56/29 SUZHOU-TELECOM-CLIENT-CENTRE APNIC ASSIGNED NON-PORTABLE ● high
58.211.251.64/29 SUZHOU-TELECOM-CLIENT-CENTRE APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SUZHOU TELECOM CLIENT” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

CH446-AP CL1840-AP HZ1312-AP LJ1711-AP LR268-AP LY1893-AP MAINT-CHINANET-JS ZL1488-AP