SHANGHAI-TELECOM

BGP inherited
Cluster stats
Netblocks6
All fragments 30 blocks across 19 clusters
Cluster ID210164859
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 12 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 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
202.96.192.8/30 SHANGHAI-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
202.96.192.12/30 SHANGHAI-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
202.96.211.16/28 SHANGHAI-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
202.96.215.0/28 SHANGHAI-TELECOM-CORP APNIC ASSIGNED NON-PORTABLE ● high
202.96.215.16/29 SHANGHAI-TELECOM-CORP APNIC ASSIGNED NON-PORTABLE ● high
202.96.240.208/30 SHANGHAI-TELECOM APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SHANGHAI 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 19 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

BY11-AP BY11-AP LL421-AP LL421-AP MAINT-CHINANET MAINT-CHINANET-SH TJ14-AP TJ14-AP TJ20-AP TJ20-AP TJ21-AP TJ21-AP