Network · data from 2026-11-12
AS2472 FR-DOM-GUYANE - Renater
Registry name: FR-DOM-GUYANE - Renater, EU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2472, 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.
| 2001:661:4000::/35 | No ROA | RIR databaseRIPE | 631 99% |
| 193.48.161.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.48.162.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.49.230.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.50.134.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.51.118.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.55.4.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 194.214.214.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 194.254.208.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 195.98.226.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 195.98.227.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS2472 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 1 are in fix.csv.
- ROA: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:661:4000::/35 | No ROA covers it. Add a ROA for AS2472, maxLength 35. |
Route objects not announced
Every route object with origin AS2472 is announced.
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.