Intersvyaz LLC

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks12 · 690 IPv4 addresses
IPv6 2 prefixes (largest 2001:7f8:20:101::208:228/128)
All fragments 97 blocks across 3 clusters
Cluster ID214586327
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

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

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.5.143.0/24 Intersvyaz LLC BGP ANNOUNCED ● high
195.208.208.26/32 Intersvyaz PEERINGDB ASSIGNED ● high
195.208.208.228/32 Intersvyaz PEERINGDB ASSIGNED ● high
2001:7f8:20:101::208:26/128 Intersvyaz PEERINGDB ASSIGNED ● high
2001:7f8:20:101::208:228/128 Intersvyaz PEERINGDB ASSIGNED ● high
62.5.192.176/28 INTERSVYAZ RIPE ASSIGNED PA ● low
81.176.200.0/25 INTERSVYAZ RIPE ASSIGNED PA ● low
87.226.231.228/30 Intersvyaz RIPE ASSIGNED PA ● low
95.167.101.0/24 Intersvyaz RIPE ASSIGNED PA ● low
194.84.149.0/29 INTERSVYAZ-NET RIPE ASSIGNED PA ● low
195.151.185.72/30 INTERSVYAZ-NET RIPE ASSIGNED PA ● low
212.176.3.176/28 INTERSVYAZ-NET RIPE ASSIGNED PA ● low

IPv6 ranges (2)

CIDR
2001:7f8:20:101::208:228/128
2001:7f8:20:101::208:26/128

Network trust

what's this?
RPKI hygiene: C how networks compare →
69.2% of checked blocks have valid RPKI ROA coverage (9 of 13)
Possible discrepancies (1)

These blocks are registered to Intersvyaz LLC 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.

95.167.101.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

AS199619 AS8342-MNT AS8369 DUMY-RIPE DUMY-RIPE MTU-NOC ROSPRINT-NCC ROSTELECOM-MNT mnt-ru-csu-1 mnt-ru-csu-1