Afranet

RENA
Registry
Cluster stats
Netblocks10
Registered in IR (5) · Germany (4) · KZ (1)
All fragments 22 blocks across 10 clusters
Cluster ID208798966
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
79.175.166.241/32 RENA RIPE ASSIGNED PA ● low
79.175.166.250/32 RENA RIPE ASSIGNED PA ● low
79.175.166.253/32 RENA RIPE ASSIGNED PA ● low
80.75.8.0/27 RENA RIPE ASSIGNED PA ● low
80.75.8.216/29 RENA RIPE ASSIGNED PA ● low
88.204.145.104/30 RENA RIPE ASSIGNED PA ● low
145.253.108.32/28 RENA-NET RIPE ASSIGNED PA ● low
178.15.15.40/29 RENA-NET RIPE ASSIGNED PA ● low
178.15.75.232/29 RENA-NET RIPE ASSIGNED PA ● low
178.15.82.232/29 RENA-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RENA” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Combined view of all 10 name-family clusters →
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

AFRA-MNT-NESH-1 ARCOR-MNT DUMY-RIPE DUMY-RIPE KNIC-MNT