URALSVIAZINFORM-PERM-NET

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks7
Record ID247344019
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.219.6.168/29 URALSVIAZINFORM-PERM-NET RIPE ASSIGNED PA ● low
83.219.14.128/29 URALSVIAZINFORM-PERM-NET RIPE ASSIGNED PA ● low
83.219.18.184/29 URALSVIAZINFORM-PERM-NET RIPE ASSIGNED PA ● low
83.219.22.248/29 URALSVIAZINFORM-PERM-NET RIPE ASSIGNED PA ● low
83.219.31.240/28 URALSVIAZINFORM-PERM-NET RIPE ASSIGNED PA ● low
212.120.164.208/29 URALSVIAZINFORM-PERM-NET RIPE ASSIGNED PA ● low
212.120.188.120/29 URALSVIAZINFORM-PERM-NET RIPE ASSIGNED PA ● low

Footprint over time

15 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-10-04

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE PI-RIPE-MNT ROSTELECOM-MNT