Network · data from 2026-11-12
AS2202 FR-RENATER-REAUMUR - Renater
Registry name: FR-RENATER-REAUMUR - Renater, EU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2202, 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.
| 134.158.112.0/21 | Invalid: origin | Other origin only | 1 0%low visibility |
| 147.210.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 193.56.108.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.56.109.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.56.110.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.56.111.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.56.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS2202 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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 134.158.112.0/21 | ROAs covering it name AS789, not AS2202. If AS2202 should announce it, add a ROA for AS2202. |
| Route object: none | 134.158.112.0/21 | Route objects for it name AS789. Add a route object with origin AS2202 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2202 whose prefix no peer sees AS2202 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.56.228.0/24 | RIPE | Valid |
| 193.56.229.0/24 | 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.