Telco-Pro-Services

BGP inherited
Cluster stats
Netblocks10
All fragments 28 blocks across 3 clusters
Cluster ID205047886
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-13

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.99.175.72/29 TELCO-PRO-SERVICES RIPE ASSIGNED PA ● low
84.244.97.160/29 TELCO-PRO-SERVICES RIPE ASSIGNED PA ● low
85.93.126.184/29 Telco-Pro-Services RIPE ASSIGNED PA ● low
85.207.103.232/29 TELCO-PRO-SERVICES RIPE ASSIGNED PA ● low
85.207.103.248/29 TELCO-PRO-SERVICES RIPE ASSIGNED PA ● low
185.24.238.96/29 Telco-Pro-Services RIPE ASSIGNED PA ● low
195.122.215.248/29 Telco-Pro-Services RIPE ASSIGNED PA ● low
213.151.77.152/29 Telco-Pro-Services RIPE ASSIGNED PA ● low
213.151.82.16/29 Telco-Pro-Services RIPE ASSIGNED PA ● low
213.151.92.184/29 Telco-Pro-Services RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

BlueTone-MNT DIALTELECOM-MNT DUMY-RIPE DUMY-RIPE