VOO TELECOM
Cluster stats
Netblocks16
All fragments 80 blocks across 3 clusters
Cluster ID193384217
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.72.36/32 VOO TELECOM PEERINGDB ASSIGNED ● high
45.68.73.225/32 Voo Telecom AP PEERINGDB ASSIGNED ● high
45.68.74.16/32 VOO TELECOM PEERINGDB ASSIGNED ● high
45.68.83.205/32 VOO TELECOM PEERINGDB ASSIGNED ● high
187.16.208.83/32 Voo Telecom AP PEERINGDB ASSIGNED ● high
187.16.212.225/32 VOO TELECOM PEERINGDB ASSIGNED ● high
187.16.214.123/32 VOO TELECOM PEERINGDB ASSIGNED ● high
200.219.147.206/32 Voo Telecom AP PEERINGDB ASSIGNED ● high
2001:12f8::208:83/128 Voo Telecom AP PEERINGDB ASSIGNED ● high
2001:12f8::212:225/128 VOO TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::214:123/128 VOO TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:2::55:205/128 VOO TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::36/128 VOO TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:225/128 Voo Telecom AP PEERINGDB ASSIGNED ● high
2001:12f8:0:9::146:16/128 VOO TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:10::206/128 Voo Telecom AP 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

AS268512 AS269713