RTK-RU

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks5 · 1,028 IPv4 addresses
Cluster ID213596456
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
79.135.248.0/24 RTK-RU RIPE ASSIGNED PA ● low
87.226.163.208/30 RTK-RU RIPE ASSIGNED PA ● low
90.154.59.0/24 RTK-RU RIPE ASSIGNED PA ● low
176.208.82.0/24 RTK-RU RIPE ASSIGNED PA ● low
178.185.238.0/24 RTK-RU 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 (5 of 5)
Possible discrepancies (4)

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

176.208.82.0/24 /24 authorized for AS12389 — PJSC Rostelecom
178.185.238.0/24 /24 authorized for AS12389 — PJSC Rostelecom
79.135.248.0/24 /24 authorized for AS12389 — PJSC Rostelecom
90.154.59.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT