Renater
FR-IPSL-LATMOS-GUYANCOURT
Data as of 2026-07-26
Registry
Cluster stats
| Netblocks | 13 · 3,072 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:660:3023::/48) |
| Cluster ID | 214634536 |
| Registry | RIPE |
| Customers | find 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
13
0 netblocks since 2026-07-05
2026-07-05
peak 13
2026-07-26
IP Ranges (13)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.52.168.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 193.52.169.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 193.52.170.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 193.52.171.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 193.52.172.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 193.52.173.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 193.52.174.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 193.52.175.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 194.254.39.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 194.254.40.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 194.254.41.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 194.254.42.0/24 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED PA | ● low |
| 2001:660:3023::/48 | FR-IPSL-LATMOS-GUYANCOURT | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:660:3023::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(13 of 13)
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