RTK
Cluster stats
Netblocks14
All fragments 128 blocks across 53 clusters
Cluster ID192177206
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 14 shared RIR contact/maintainer handles
Registry names 6 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.79.248.0/24 RTK-NET RIPE ASSIGNED PA ● low
59.154.186.64/30 RTK APNIC ASSIGNED NON-PORTABLE ● low
82.114.67.232/29 RTK RIPE ASSIGNED PA ● low
82.114.68.224/29 RTK RIPE ASSIGNED PA ● low
82.114.72.0/28 RTK RIPE ASSIGNED PA ● low
82.114.73.104/29 RTK RIPE ASSIGNED PA ● low
83.218.120.0/24 RTK-NET RIPE ASSIGNED PA ● low
91.190.58.248/29 RTK-net RIPE ASSIGNED PA ● low
94.25.19.0/24 RTK RIPE ASSIGNED PA ● low
159.100.96.8/29 RTK RIPE LEGACY ● low
188.128.26.64/28 RTK_net RIPE ASSIGNED PA ● low
213.85.56.52/30 rtk-net RIPE ASSIGNED PA ● low
213.163.123.224/29 RTK RIPE ASSIGNED PA ● low
213.178.70.128/26 RTK-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (12 of 14)
Possible discrepancies (2)

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

94.25.19.0/24 /24 authorized for AS12389 — PJSC Rostelecom
37.79.248.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

AS2588-MNT DUMY-RIPE DUMY-RIPE MAINT-OPTUSCOM-AP MNT-RTK NOC-KIS OA3-AP OA3-AP PTK-MNT ROSTELECOM-MNT SNLV-MNT TNF-MNT +2 more