VSI-MSN-REGION
Unresolved
Cluster stats
Netblocks12
All fragments 13 blocks across 2 clusters
Cluster ID192002402
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
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-06

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.82.43.128/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.45.0/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.46.0/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.46.128/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.47.0/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.47.128/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.50.0/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.50.128/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.51.0/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.51.128/25 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.58.0/23 VSI-MSN-REGION RIPE ASSIGNED PA ● low
80.82.60.0/25 VSI-MSN-REGION 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 (12 of 12)
Possible discrepancies (1)

These blocks are registered to VSI-MSN-REGION 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.

80.82.58.0/23 /23 authorized for AS21017 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT