Vyacheslav V. Vovk
Data as of 2026-07-26
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 · 512 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:67c:5e8::/48) |
| Cluster ID | 214700790 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.201.116.0/23 | Vyacheslav V. Vovk | RIPE | ASSIGNED PI | ● high |
| 2001:67c:5e8::/48 | Vyacheslav V. Vovk | RIPE | ASSIGNED PI | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:67c:5e8::/48 |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
Possible discrepancies (1)
These blocks are registered to Vyacheslav V. Vovk 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.
| 2001:67c:5e8::/48 /48 | authorized for AS28681 — KhmelnitskInfocom LTD |
NIC Handles
DUMY-RIPE
DUMY-RIPE
KM-MNT
ORG-VOVK2-RIPE
RIPE-NCC-END-MNT