Vimpel Com
VimpelCom
Cluster stats
| Netblocks | 30 |
| All fragments | 56 blocks across 23 clusters |
| Cluster ID | 192324719 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
30
0 netblocks since 2026-07-05
2026-07-05
peak 30
2026-07-06
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 36.255.56.171/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 80.81.192.243/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 80.249.209.153/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 101.203.89.119/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 103.203.158.173/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 123.255.91.209/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.95/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 193.239.118.254/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 194.68.123.151/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 194.68.128.151/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 195.66.224.205/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 198.32.118.28/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 210.173.177.80/32 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:504:f::3216:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::c90:0:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a500:3216:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::c90:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:fe::151/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:ff::151/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a500:3216:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a1d1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:7:1::3216:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:7::3216:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::3216:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2403:c780:b800:bb00::3216:1/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:95/128 | VimpelCom | PEERINGDB | ASSIGNED | ● high |
| 80.237.90.144/28 | VIMPELCOM-NET | RIPE | ASSIGNED PA | ● low |
| 92.50.218.248/29 | Vimpelcom | RIPE | ASSIGNED PA | ● low |
| 94.25.43.136/30 | Vimpelcom | RIPE | ASSIGNED PA | ● low |
| 94.25.99.72/29 | Vimpelcom | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
86.7%
of checked blocks have valid RPKI ROA coverage
(26 of 30)
No discrepancies found among checked blocks.
NIC Handles
AS3216
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT
TRANSTELECOM-MNT