Shunde-Telecom

BGP inherited
Cluster stats
Netblocks6
All fragments 9 blocks across 2 clusters
Cluster ID212415977
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name 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-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
121.9.15.16/28 Shunde-Telecom APNIC Allocated non-portable ● low
202.104.30.128/26 Shunde-Telecom APNIC ASSIGNED NON-PORTABLE ● low
202.104.31.4/30 Shunde-Telecom APNIC Allocated non-portable ● low
202.104.31.36/30 Shunde-Telecom APNIC Allocated non-portable ● low
202.104.31.52/30 Shunde-Telecom APNIC Allocated non-portable ● low
202.104.31.120/30 Shunde-Telecom APNIC Allocated non-portable ● low

Possibly related to this organisation

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

Network trust

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

NIC Handles

FS-AP IC83-AP MAINT-CHINANET-GD