Voskhod
Registry
Cluster stats
| Netblocks | 7 · 281 IPv4 addresses |
| All fragments | 9 blocks across 3 clusters |
| Cluster ID | 209491473 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 5 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.64.104.64/29 | NET-VOSKHOD | RIPE | ASSIGNED PA | ● low |
| 80.64.104.152/29 | NET-VOSKHOD | RIPE | ASSIGNED PA | ● low |
| 89.175.8.208/30 | VOSKHOD | RIPE | ASSIGNED PA | ● low |
| 94.25.6.124/30 | Voskhod | RIPE | ASSIGNED PA | ● low |
| 95.167.74.244/30 | Voskhod | RIPE | ASSIGNED PA | ● low |
| 213.85.3.68/30 | voskhod-net | RIPE | ASSIGNED PA | ● low |
| 213.243.116.0/24 | VOSKHOD-NET | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Voskhod” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- VOSKHOD_ORIEL 1 blocks
- VOSKHOD-METIZ 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- TOOVOSKHODORIEL via JSC Kazakhtelecom sub-allocation
- VOSKHOD_ORIEL via JSC Kazakhtelecom sub-allocation
- Khleboobedinenie_Voskhod via PJSC Rostelecom sub-allocation
- LINXDC-SPB-VOSKHODLAWFIRM-T067205 via Svyaz VSD LLC sub-allocation
- Assignment-FGBU-NII-Voskhod-EGISZ sub-allocation
- Assignment-FGBU-NII-Voskhod-1 sub-allocation
- Assignment-FGBU-NII-Voskhod-2 sub-allocation
- CHUTPP-VOSKHOD-SERVIS-BREST via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
Network trust
what's this?
RPKI hygiene: B
how networks compare →
85.7%
of checked blocks have valid RPKI ROA coverage
(6 of 7)
Possible discrepancies (1)
These blocks are registered to Voskhod 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.
| 213.243.116.0/24 /24 | authorized for AS25159 — PJSC MegaFon |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MEGAFON-AUTO-MNT
MEGAFON-RIPE-MNT
MF-MOSCOW-MNT
MTU-NOC
RASCOM-MNT
ROSTELECOM-MNT
cnt-mnt