Vamo Telecom
Cluster stats
| Netblocks | 18 |
| All fragments | 20 blocks across 2 clusters |
| Cluster ID | 191585411 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (18)
⬇ 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 |
| 138.97.196.0/22 | VAMO TELECOM | BGP | ANNOUNCED | ● high |
| 138.97.196.0/23 | VAMO TELECOM | BGP | ANNOUNCED | ● high |
| 138.97.198.0/23 | VAMO TELECOM | BGP | ANNOUNCED | ● 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 |
| 2804:2400::/32 | VAMO TELECOM | BGP | ANNOUNCED | ● high |
| 2804:2400::/32 | UNKNOWN | LACNIC | allocated | ● medium |
| 80.121.172.76/30 | VAMO-HWY-AT | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
No discrepancies found among checked blocks.
NIC Handles
AS264195
AS264195
AS8447-MNT
DUMY-RIPE
DUMY-RIPE