RU-SOVINTEL-MSK-YANDEX-NET

BGP inherited
Cluster stats
Netblocks6
All fragments 9 blocks across 4 clusters
Cluster ID205078696
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.231.1.8/29 RU-SOVINTEL-MSK-YaNDeX-NET RIPE ASSIGNED PA ● low
194.186.31.168/29 RU-SOVINTEL-MSK-yaNDeX-NET RIPE ASSIGNED PA ● low
195.68.142.160/27 RU-SOVINTEL-MSK-YANDEX-NET RIPE ASSIGNED PA ● low
195.68.142.224/27 RU-SOVINTEL-MSK-YANDEX-NET RIPE ASSIGNED PA ● low
2a00:1248:5001:4::/64 RU-SOVINTEL-MSK-YANDEX-NET RIPE ASSIGNED ● low
2a00:1248:5001:5::/64 RU-SOVINTEL-MSK-YANDEX-NET RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RU SOVINTEL MSK YANDEX” — 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.
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.

NIC Handles

DUMY-RIPE DUMY-RIPE SOVINTEL-MNT