RADNET
Cluster stats
Netblocks8
All fragments 43 blocks across 8 clusters
Cluster ID192062249
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-06

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.183.92.0 – 62.183.99.255 RADNET RIPE ASSIGNED PA ● low
83.239.224.0/20 RADNET RIPE ASSIGNED PA ● low
85.174.240.0/20 RADNET RIPE AGGREGATED-BY-LIR ● low
85.174.248.0/23 RADNET RIPE ASSIGNED PA ● low
94.233.152.0/21 RADNET RIPE ASSIGNED PA ● low
94.233.160.0/20 RADNET RIPE ASSIGNED PA ● low
121.200.234.224/29 RADNET APNIC ASSIGNED NON-PORTABLE ● low
178.34.192.0/20 RADNET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
Possible discrepancies (5)

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

83.239.224.0/20 /20 authorized for AS25490 — PJSC Rostelecom
94.233.160.0/20 /20 authorized for AS25490 — PJSC Rostelecom
178.34.192.0/20 /20 authorized for AS12389 — PJSC Rostelecom
85.174.240.0/20 /20 authorized for AS25490 — PJSC Rostelecom
85.174.248.0/23 /23 authorized for AS25490 — PJSC Rostelecom

NIC Handles

AV428-AP DUMY-RIPE DUMY-RIPE MAINT-VOCUS-AU ROSTELECOM-MNT STC-MNT VPL1-AP VPL1-AP