Deep Telecom
BGP inherited
Cluster stats
Netblocks8
All fragments 137 blocks across 33 clusters
Cluster ID191810533
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.82.2/32 Deep Telecom PEERINGDB ASSIGNED ● high
45.162.112.0/22 Deep Telecom BGP ANNOUNCED ● high
177.52.38.77/32 Deep Telecom PEERINGDB ASSIGNED ● high
187.16.215.60/32 Deep Telecom PEERINGDB ASSIGNED ● high
2001:12f8::215:60/128 Deep Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:2::54:2/128 Deep Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:6::26:8505/128 Deep Telecom PEERINGDB ASSIGNED ● high
2804:5240::/32 Deep Telecom BGP ANNOUNCED ● high

Network trust

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

NIC Handles

AS268505 AS268505