JSC Pursvyaz

BGP inherited
Cluster stats
Netblocks10 · 10,231 IPv4 addresses
Cluster ID208796062
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
79.140.240.0/23 JSC Pursvyaz BGP ANNOUNCED ● high
79.140.243.0/24 JSC Pursvyaz BGP ANNOUNCED ● high
79.140.244.0/22 JSC Pursvyaz BGP ANNOUNCED ● high
79.140.248.0/23 JSC Pursvyaz BGP ANNOUNCED ● high
79.140.250.0/23 JSC Pursvyaz BGP ANNOUNCED ● high
79.140.252.0/24 JSC Pursvyaz BGP ANNOUNCED ● high
79.140.254.0/23 JSC Pursvyaz BGP ANNOUNCED ● high
79.140.240.0/20 JSC Pursvyaz RIPE ALLOCATED PA ● low
79.140.240.0 – 79.140.249.255 JSC Pursvyaz RIPE ASSIGNED PA ● low
2a0a:4f40::/32 JSC Pursvyaz RIPE ALLOCATED-BY-RIR ● low

Possibly related to this organisation

what's this?
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.
  • Pursvyaz via PJSC Rostelecom sub-allocation

NIC Handles

AS43908 DUMY-RIPE DUMY-RIPE ORG-JP8-RIPE PSV-MNT PSV-MNT RIPE-NCC-HM-MNT