VESCOM-B-V
VESCOM-B-V-GTT
Cluster stats
| Netblocks | 18 |
| All fragments | 19 blocks across 2 clusters |
| Cluster ID | 192645289 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.253.116.200/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.221.20.88/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.118.176/30 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.133.104/30 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.133.108/30 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.144.0/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.145.40/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.172.112/30 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.201.8/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.201.16/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.201.24/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.202.120/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.207.32/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.216.32/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.216.136/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.216.144/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 212.222.217.56/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
| 213.39.78.208/29 | VESCOM-B-V-GTT | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
94.4%
of checked blocks have valid RPKI ROA coverage
(17 of 18)
No discrepancies found among checked blocks.
NIC Handles
AS3257-IPAM-MNT
DUMY-RIPE
DUMY-RIPE