Telecom Center
Cluster stats
Netblocks9
All fragments 10 blocks across 2 clusters
Cluster ID192040372
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.9.49.31/32 Telecom Center PEERINGDB ASSIGNED ● high
146.185.252.26/32 Telecom Center PEERINGDB ASSIGNED ● high
185.1.152.137/32 Telecom Center PEERINGDB ASSIGNED ● high
185.232.60.51/32 Telecom Center PEERINGDB ASSIGNED ● high
193.27.37.27/32 Telecom Center PEERINGDB ASSIGNED ● high
193.27.39.134/32 Telecom Center PEERINGDB ASSIGNED ● high
222.68.190.124/30 TELECOM-CENTER APNIC ASSIGNED NON-PORTABLE ● high
80.166.122.112/28 TELECOM-CENTER-NET RIPE ASSIGNED PA ● low
83.89.150.144/29 TELECOM-CENTER-NET RIPE ASSIGNED PA ● low

Network trust

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

NIC Handles

AS62423 CZZ1-AP CZZ1-AP DUMY-RIPE DUMY-RIPE MAINT-CHINANET-SH TDK-MNT