Vamo Telecom

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks12
IPv6 6 prefixes (largest 2001:12f8:0:31::53/128)
Cluster ID214591473
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
12 -6 netblocks since 2026-07-05
2026-07-05 peak 18 2026-07-26

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.74.146/32 Vamo Telecom PEERINGDB ASSIGNED ● high
45.68.76.111/32 Vamo Telecom PEERINGDB ASSIGNED ● high
45.227.1.53/32 Vamo Telecom PEERINGDB ASSIGNED ● high
187.16.215.61/32 Vamo Telecom PEERINGDB ASSIGNED ● high
187.16.215.183/32 Vamo Telecom PEERINGDB ASSIGNED ● high
187.16.220.29/32 Vamo Telecom PEERINGDB ASSIGNED ● high
2001:12f8::215:61/128 Vamo Telecom PEERINGDB ASSIGNED ● high
2001:12f8::215:183/128 Vamo Telecom PEERINGDB ASSIGNED ● high
2001:12f8::220:29/128 Vamo Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:9::146:146/128 Vamo Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:9::148:111/128 Vamo Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:31::53/128 Vamo Telecom PEERINGDB ASSIGNED ● high

IPv6 ranges (6)

Network trust

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

NIC Handles

AS264195