Voskhod

Data as of 2026-09-13
Registry
This organisation
Netblocks7 · 288 IPv4 addresses
Also registered under this name 9 netblocks across 3 separate records
Record ID241156029
RegistryRIPE
Customerssee who runs inside 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 · report an issue

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

Footprint over time

10 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-09-13

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