Network · data from 2026-11-12
AS8528 RENAULT Renault SAS
Registry name: RENAULT Renault SAS, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8528, 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.
| 193.236.132.0/24 | No ROA | None | 672 100% |
| 193.236.134.0/24 | No ROA | None | 672 100% |
| 193.236.133.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 193.236.135.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 138.21.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 138.21.119.0/24 | Valid | RIR databaseNTTCOM, RIPE | 673 100% |
| 138.21.148.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.8.143.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 138.21.3.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 138.21.4.0/24 | Valid | RIR databaseNTTCOM, RIPE | 672 100% |
| 138.21.12.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 138.21.23.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 138.21.50.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 138.21.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 138.21.113.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 138.21.117.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.194.132.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.194.135.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.41.4.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 194.146.54.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a00:7ec0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7ec0:1::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS8528 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 22 are in fix.csv.
- ROA: none4
- Route object: none2
- Route object: RIR2
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.236.132.0/24 | No ROA covers it. Add a ROA for AS8528, maxLength 24. |
| Route object: none | 193.236.132.0/24 | No route object for it. Add a route object with origin AS8528 in the RIR database for the space. |
| ROA: none | 193.236.134.0/24 | No ROA covers it. Add a ROA for AS8528, maxLength 24. |
| Route object: none | 193.236.134.0/24 | No route object for it. Add a route object with origin AS8528 in the RIR database for the space. |
| ROA: none | 193.236.133.0/24 | No ROA covers it. Add a ROA for AS8528, maxLength 24. |
| Route object: RIR | 193.236.133.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 193.236.135.0/24 | No ROA covers it. Add a ROA for AS8528, maxLength 24. |
| Route object: RIR | 193.236.135.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8528 whose prefix no peer sees AS8528 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.21.18.0/24 | RIPE | Valid |
| 138.21.34.0/24 | RIPE | Valid |
| 138.21.37.0/24 | NTTCOM, RIPE | Valid |
| 138.21.47.0/24 | NTTCOM, RIPE | Valid |
| 138.21.56.0/24 | RIPE | Valid |
| 138.21.78.0/24 | RIPE | Valid |
| 193.53.38.0/24 | RIPE | No ROA |
| 193.56.119.0/24 | RIPE | No ROA |
| 193.57.10.0/24 | RIPE | No ROA |
| 193.57.24.0/24 | RIPE | No ROA |
| 193.57.26.0/24 | RIPE | No ROA |
| 193.194.134.0/24 | RIPE | Valid |
| 194.146.27.0/24 | RIPE | No ROA |
| 2a00:7ec0::/48 | RIPE | Invalid: maxLength |
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.