67 Telecom
Cluster stats
Netblocks16
All fragments 37 blocks across 2 clusters
Cluster ID193386309
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

Footprint over time

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

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.184.144.71/32 67 Telecom PEERINGDB ASSIGNED ● high
45.227.2.30/32 67 Telecom PEERINGDB ASSIGNED ● high
177.52.38.199/32 67 Telecom PEERINGDB ASSIGNED ● high
187.16.204.5/32 67 Telecom PEERINGDB ASSIGNED ● high
187.16.213.83/32 67 Telecom PEERINGDB ASSIGNED ● high
187.16.213.200/32 67 Telecom PEERINGDB ASSIGNED ● high
200.219.141.29/32 67 Telecom PEERINGDB ASSIGNED ● high
200.219.144.5/32 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8::213:83/128 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8::213:200/128 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:5::29/128 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:6::6:1614/128 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:7::5/128 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:13::71/128 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:27::5/128 67 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:32::30/128 67 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 (16 of 16)
No discrepancies found among checked blocks.

NIC Handles

AS61614