Renesys
Cluster stats
Netblocks13
All fragments 15 blocks across 3 clusters
Cluster ID193384498
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.194.211/32 Renesys PEERINGDB ASSIGNED ● high
195.66.225.224/32 Renesys PEERINGDB ASSIGNED ● high
198.32.124.108/32 Renesys PEERINGDB ASSIGNED ● high
198.32.176.91/32 Renesys PEERINGDB ASSIGNED ● high
203.190.230.21/32 Renesys PEERINGDB ASSIGNED ● high
206.72.210.34/32 Renesys PEERINGDB ASSIGNED ● high
2001:478:124::108/128 Renesys PEERINGDB ASSIGNED ● high
2001:504:d::5b/128 Renesys PEERINGDB ASSIGNED ● high
2001:504:13::210:34/128 Renesys PEERINGDB ASSIGNED ● high
2001:7f8::fc55:0:1/128 Renesys PEERINGDB ASSIGNED ● high
2001:7f8:4::fc55:1/128 Renesys PEERINGDB ASSIGNED ● high
2001:de8:5::6:4597:1/128 Renesys PEERINGDB ASSIGNED ● high
85.112.31.64/28 RENESYS RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
61.5% of checked blocks have valid RPKI ROA coverage (8 of 13)
No discrepancies found among checked blocks.

NIC Handles

AS34135 DUMY-RIPE DUMY-RIPE MNT-AS23148