Direct Telecom
Cluster stats
Netblocks22
All fragments 192 blocks across 2 clusters
Cluster ID193384679
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (22)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.73.23/32 Direct Telecom PEERINGDB ASSIGNED ● high
45.68.74.120/32 Direct Telecom PEERINGDB ASSIGNED ● high
45.184.144.227/32 Direct Telecom PEERINGDB ASSIGNED ● high
45.227.0.71/32 Direct Telecom PEERINGDB ASSIGNED ● high
80.81.195.169/32 Direct Telecom PEERINGDB ASSIGNED ● high
80.249.211.4/32 Direct Telecom PEERINGDB ASSIGNED ● high
187.16.209.113/32 Direct Telecom PEERINGDB ASSIGNED ● high
187.16.211.29/32 Direct Telecom PEERINGDB ASSIGNED ● high
195.66.231.165/32 Direct Telecom PEERINGDB ASSIGNED ● high
200.219.138.15/32 Direct Telecom PEERINGDB ASSIGNED ● high
206.82.105.114/32 Direct Telecom PEERINGDB ASSIGNED ● high
2001:504:36:0:4:b2:0:1/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:7f8::4:b2:0:1/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:26:4997:1/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:7f8:4::4:b25:1/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:12f8::209:113/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:12f8::211:29/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:23/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:9::146:120/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:13::227/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:29::15/128 Direct Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:30::71/128 Direct Telecom PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (22 of 22)
No discrepancies found among checked blocks.

NIC Handles

AS264997