Renater

FR-CENTRALE-SUPELEC
Data as of 2026-07-26
Registry
Cluster stats
Netblocks7 · 1,536 IPv4 addresses
IPv6 1 prefix (largest 2001:660:3105::/48)
All fragments 216 blocks across 99 clusters
Cluster ID214647616
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-26

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.48.224.0/24 FR-CENTRALE-SUPELEC RIPE ASSIGNED PA ● low
193.48.225.0/24 FR-CENTRALE-SUPELEC RIPE ASSIGNED PA ● low
193.54.24.0/24 FR-CENTRALE-SUPELEC RIPE ASSIGNED PA ● low
193.54.192.0/24 FR-CENTRALE-SUPELEC RIPE ASSIGNED PA ● low
193.54.193.0/24 FR-CENTRALE-SUPELEC RIPE ASSIGNED PA ● low
193.54.194.0/24 FR-CENTRALE-SUPELEC RIPE ASSIGNED PA ● low
2001:660:3105::/48 FR-CENTRALE-SUPELEC RIPE ASSIGNED ● low

IPv6 ranges (1)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
RPKI-inferred operator Renater
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE RENATER-MNT