Renater
FR-U-MAINE-LEMANS
Registry
Cluster stats
| Netblocks | 9 · 2,295 IPv4 addresses |
| All fragments | 1,761 blocks across 120 clusters |
| Cluster ID | 208841822 |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
9
0 netblocks since 2026-07-05
2026-07-05
peak 9
2026-07-19
IP Ranges (9)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.50.132.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 193.52.28.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 193.52.29.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 193.52.30.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 193.52.31.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 195.221.215.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 195.221.243.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 195.221.244.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
| 195.221.245.0/24 | FR-U-MAINE-LEMANS | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “FR U” — 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.
- FR-U-GIE-IRIS--LB_INTERNET 469 blocks
- FR-U-LORRAINE 167 blocks
- FR-U-NANTES 65 blocks
- FR-U-PARISSUD-ORSAY 55 blocks
- FR-U-MONTPELLIER 46 blocks
- FR-U-ORLEANS-CENTRE 40 blocks
- FR-U-LILLE 39 blocks
- FR-U-3-TOULOUSE 37 blocks
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(9 of 9)
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