VSI-FIX-ADDR
Unresolved
Cluster stats
Netblocks9
All fragments 55 blocks across 17 clusters
Cluster ID191997904
RegistryRIPE
Customersfind 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

Footprint over time

2 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.82.34.148/30 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
80.82.35.0/24 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
80.82.41.32 – 80.82.41.55 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
80.82.41.224/27 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
80.82.42.168/29 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
80.82.54.0/23 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
80.82.62.0/23 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
88.83.200.0/23 VSI-FIX-ADDR RIPE ASSIGNED PA ● low
88.83.202.0/23 VSI-FIX-ADDR RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (5)

These blocks are registered to VSI-FIX-ADDR 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.

88.83.200.0/23 /23 authorized for AS21017 — PJSC Rostelecom
88.83.202.0/23 /23 authorized for AS21017 — PJSC Rostelecom
80.82.54.0/23 /23 authorized for AS21017 — PJSC Rostelecom
80.82.62.0/23 /23 authorized for AS21017 — PJSC Rostelecom
80.82.35.0/24 /24 authorized for AS21017 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT