V8 Telecom
Cluster stats
Netblocks16
All fragments 38 blocks across 2 clusters
Cluster ID193384912
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 (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.80.168/32 V8 Telecom PEERINGDB ASSIGNED ● high
45.68.81.240/32 V8 Telecom PEERINGDB ASSIGNED ● high
45.184.144.57/32 V8 Telecom PEERINGDB ASSIGNED ● high
45.184.144.113/32 V8 Telecom PEERINGDB ASSIGNED ● high
187.16.214.245/32 V8 Telecom PEERINGDB ASSIGNED ● high
187.16.220.173/32 V8 Telecom PEERINGDB ASSIGNED ● high
200.219.139.38/32 V8 Telecom PEERINGDB ASSIGNED ● high
200.219.139.41/32 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8::214:245/128 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8::220:173/128 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:2::168/128 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:2::53:240/128 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:3::38/128 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:3::41/128 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:13::57/128 V8 Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:13::113/128 V8 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

AS270888