Network · data from 2026-11-12
AS2072 FR-RENATER-REVE - Renater
Registry name: FR-RENATER-REVE - Renater, EU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2072, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 192.93.214.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.4.251.0/24 | Valid | None | 670 100% |
AS-SET
AS2072 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 42 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced40
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.93.214.0/24 | No ROA covers it. Add a ROA for AS2072, maxLength 24. |
| Route object: none | 185.4.251.0/24 | No route object for it. Add a route object with origin AS2072 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2072 whose prefix no peer sees AS2072 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 157.159.0.0/16 | RIPE | No ROA |
| 193.49.22.0/24 | RIPE | Valid |
| 193.49.163.0/24 | RIPE | Valid |
| 193.50.0.0/24 | RIPE | Valid |
| 193.50.1.0/24 | RIPE | Valid |
| 193.50.2.0/24 | RIPE | Valid |
| 193.50.3.0/24 | RIPE | Invalid: origin |
| 193.50.67.0/24 | RIPE | Valid |
| 193.50.68.0/24 | RIPE | Valid |
| 193.50.201.0/24 | RIPE | Valid |
| 193.51.65.0/24 | RIPE | Valid |
| 193.51.66.0/24 | RIPE | Valid |
| 193.51.128.0/24 | RIPE | Invalid: origin |
| 193.51.128.48/29 | RIPE | Valid |
| 193.51.128.56/29 | RIPE | Valid |
| 193.51.128.128/25 | RIPE | Valid |
| 193.54.195.0/24 | RIPE | Valid |
| 193.54.225.0/24 | RIPE | Valid |
| 194.57.183.0/24 | RIPE | Valid |
| 194.57.241.0/24 | RIPE | Valid |
| 194.199.83.0/24 | RIPE | Valid |
| 194.199.84.0/24 | RIPE | Valid |
| 194.199.85.0/24 | RIPE | Valid |
| 194.199.86.0/24 | RIPE | Valid |
| 194.199.87.0/24 | RIPE | Valid |
| 194.199.88.0/24 | RIPE | Valid |
| 194.199.89.0/24 | RIPE | Valid |
| 194.199.90.0/24 | RIPE | Valid |
| 195.83.166.0/24 | RIPE | Valid |
| 195.83.221.0/24 | RIPE | Valid |
| 195.83.222.0/24 | RIPE | Valid |
| 195.83.223.0/24 | RIPE | Valid |
| 195.83.224.0/24 | RIPE | Invalid: origin |
| 195.221.157.0/24 | RIPE | Valid |
| 195.221.158.0/24 | RIPE | Valid |
| 195.221.159.0/24 | RIPE | Valid |
| 195.221.160.0/24 | RIPE | Valid |
| 195.221.161.0/24 | RIPE | Valid |
| 195.221.162.0/24 | RIPE | Valid |
| 2001:660:3020::/48 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.