VOO TELECOM

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks11 · 1,029 IPv4 addresses
IPv6 5 prefixes (largest 2001:12f8:0:2::55:205/128)
All fragments 18 blocks across 3 clusters
Cluster ID233772992
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

10 weekly snapshots · JSON
11 -45 netblocks since 2026-07-05
2026-07-05 peak 56 2026-08-30

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.72.36/32 VOO TELECOM 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.212.225/32 VOO TELECOM PEERINGDB ASSIGNED ● high
187.16.214.123/32 VOO TELECOM 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::146:16/128 VOO TELECOM PEERINGDB ASSIGNED ● high
45.161.184.0/22 VOO TELECOM ARIN ALLOCATED ● low

IPv6 ranges (5)

CIDR
2001:12f8:0:2::55:205/128
2001:12f8:0:9::146:16/128
2001:12f8:0:9::36/128
2001:12f8::212:225/128
2001:12f8::214:123/128

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
Possible discrepancies (1)

These blocks are registered to VOO TELECOM but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

45.161.184.0/22 /22 authorized for AS268512 — AS268512

NIC Handles

10554177000193 AS268512 CMSME57 CMSME57 CMSME57