Renater
FR-PRES-U-2-TOULOUSE
Data as of 2026-10-11
Registry
This organisation
| Netblocks | 17 · 4,224 IPv4 addresses |
| Also registered under this name | 28 netblocks across 2 separate records |
| Record ID | 246878230 |
| Registry | RIPE |
| Customers | see who runs inside 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 | |
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.51.18.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.51.175.0/25 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.54.227.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.168.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.169.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.170.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.171.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.172.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.173.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.174.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 193.55.175.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 194.167.149.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 194.167.150.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 194.167.151.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 195.98.233.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 195.98.234.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
| 195.221.137.0/24 | FR-PRES-U-2-TOULOUSE | RIPE | ASSIGNED PA | ● low |
Footprint over time
16 weekly snapshots · JSON
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-10-11
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(17 of 17)
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