No.31, Jin-rong Street

SUZHOU-TELECOM-MANGJIAN-HALL
BGP inherited
Cluster stats
Netblocks6
All fragments 894 blocks across 691 clusters
Cluster ID206572052
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
222.92.24.160/30 SUZHOU-TELECOM-MANGJIAN-HALL APNIC ASSIGNED NON-PORTABLE ● high
222.92.24.164/30 SUZHOU-TELECOM-MANGJIAN-HALL APNIC ASSIGNED NON-PORTABLE ● high
222.92.24.172/30 SUZHOU-TELECOM-MANGJIAN-HALL APNIC ASSIGNED NON-PORTABLE ● high
222.92.24.176/30 SUZHOU-TELECOM-MANGJIAN-HALL APNIC ASSIGNED NON-PORTABLE ● high
222.92.24.180/30 SUZHOU-TELECOM-MANGJIAN-HALL APNIC ASSIGNED NON-PORTABLE ● high
222.92.24.184/30 SUZHOU-TELECOM-MANGJIAN-HALL APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SUZHOU TELECOM” — 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.
Combined view of all 691 name-family clusters →
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

CH446-AP MAINT-CHINANET-JS WX828-AP WX829-AP WX830-AP WX833-AP WX834-AP WX835-AP