URALTC
Cluster stats
Netblocks15
Cluster ID191969375
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (15)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.91.32.0/21 URALTC RIPE ASSIGNED PA ● low
81.91.47.0/25 URALTC RIPE ASSIGNED PA ● low
81.91.52.96/27 URALTC RIPE ASSIGNED PA ● low
81.91.53.96/27 URALTC RIPE ASSIGNED PA ● low
81.91.53.192/27 URALTC RIPE ASSIGNED PA ● low
81.91.56.224/27 URALTC RIPE ASSIGNED PA ● low
81.91.57.0 – 81.91.59.255 URALTC RIPE ASSIGNED PA ● low
81.91.60.0/23 URALTC RIPE ASSIGNED PA ● low
85.235.32.128/25 URALTC RIPE ASSIGNED PA ● low
85.235.34.128/25 URALTC RIPE ASSIGNED PA ● low
85.235.37.0/24 URALTC RIPE ASSIGNED PA ● low
85.235.38.0/24 URALTC RIPE ASSIGNED PA ● low
85.235.44.192 – 85.235.45.255 URALTC RIPE ASSIGNED PA ● low
85.235.46.0/27 URALTC RIPE ASSIGNED PA ● low
85.235.53.0/24 URALTC RIPE ASSIGNED PA ● low

Network trust

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

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

81.91.32.0/21 /21 authorized for AS25086 — MTS PJSC
81.91.57.0 – 81.91.59.255 /22 authorized for AS25086 — MTS PJSC
81.91.60.0/23 /23 authorized for AS25086 — MTS PJSC
85.235.44.192 – 85.235.45.255 /24 authorized for AS25086 — MTS PJSC
85.235.38.0/24 /24 authorized for AS25086 — MTS PJSC
85.235.37.0/24 /24 authorized for AS25086 — MTS PJSC
85.235.53.0/24 /24 authorized for AS25086 — MTS PJSC

NIC Handles

DUMY-RIPE DUMY-RIPE UTC-MNT