RU-RTK
Cluster stats
| Netblocks | 30 |
| All fragments | 95 blocks across 22 clusters |
| Cluster ID | 192091832 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
Footprint over time
2 weekly snapshots · JSON
30
0 netblocks since 2026-07-05
2026-07-05
peak 30
2026-07-06
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2.63.247.144/28 | RU-RTK | RIPE | SUB-ALLOCATED PA | ● low |
| 79.135.229.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.64.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.65.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.66.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.67.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.68.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.69.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.70.0/28 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.72.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.78.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.79.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.80.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.81.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.82.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.84.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.86.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.87.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.88.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.89.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 83.171.93.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 85.175.109.196/30 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 89.250.170.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 95.167.254.0/23 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 176.208.78.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 176.211.117.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 176.211.118.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 213.59.199.146 – 213.59.199.161 | RU-RTK | RIPE | SUB-ALLOCATED PA | ● low |
| 217.107.83.0/24 | RU-RTK | RIPE | ASSIGNED PA | ● low |
| 217.107.114.0/24 | RU-RTK | 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
(30 of 30)
Possible discrepancies (26)
These blocks are registered to RU-RTK 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.
| 95.167.254.0/23 /23 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.64.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.65.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.66.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.68.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.72.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.78.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.82.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.80.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.81.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.84.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.86.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.88.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.87.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 83.171.69.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
+11 more — see the REST API
NIC Handles
AS8997-MNT
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT