URALSIB-LAN

BGP inherited
Cluster stats
Netblocks8
Cluster ID210341576
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.28.165.92/30 URALSIB-LAN RIPE ASSIGNED PA ● low
79.134.195.76/30 URALSIB-LAN RIPE ASSIGNED PA ● low
79.134.206.32/30 URALSIB-LAN RIPE ASSIGNED PA ● low
79.134.209.96/30 URALSIB-LAN RIPE ASSIGNED PA ● low
79.134.209.128/30 URALSIB-LAN RIPE ASSIGNED PA ● low
79.134.214.148/30 URALSIB-LAN RIPE ASSIGNED PA ● low
79.134.221.208/30 URALSIB-LAN RIPE ASSIGNED PA ● low
82.140.99.88/30 UralSib-LAN RIPE ASSIGNED PA ● 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-MF-NWGSM OBIT-MNT PSTAR-MNT