Network · data from 2026-11-12
AS199636 FREEBOXPRO Free Pro SAS
Registry name: FREEBOXPRO Free Pro SAS, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199636, 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.
| 149.232.192.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 45.80.8.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.80.20.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.80.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.80.32.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 82.96.128.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 88.202.236.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 88.212.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.200.240.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.203.92.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 95.178.88.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 130.180.208.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 141.255.128.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.44.88.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.91.220.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.146.220.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 212.114.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 2a05:6e00::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS199636 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 | 149.232.192.0/19 | No ROA covers it. Add a ROA for AS199636, maxLength 19. |
Route objects not announced
Every route object with origin AS199636 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.