Network · data from 2026-11-12
AS53306 Outscale INC
Registry name: OUTSCALE-INC - OUTSCALE INC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS53306, 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.
| 157.250.8.0/22 | No ROA | Nonecovered by 157.250.0.0/18 | 673 100% |
| 157.250.12.0/23 | No ROA | Nonecovered by 157.250.0.0/18 | 673 100% |
| 157.250.14.0/23 | No ROA | Nonecovered by 157.250.0.0/18 | 673 100% |
| 157.250.16.0/20 | No ROA | Nonecovered by 157.250.0.0/18 | 673 100% |
| 157.250.32.0/19 | No ROA | Nonecovered by 157.250.0.0/18 | 671 100% |
| 157.250.63.0/24 | No ROA | Nonecovered by 157.250.0.0/18 | 671 100% |
| 199.244.92.0/23 | No ROA | Nonecovered by 199.244.92.0/22 | 671 100% |
| 216.168.192.0/19 | No ROA | RIR databaseARIN | 671 100% |
AS-SET
AS53306's PeeringDB record names no 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 17 are in fix.csv.
- ROA: none8
- Route object: none7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 157.250.8.0/22 | No ROA covers it. Add a ROA for AS53306, maxLength 22. |
| Route object: none | 157.250.8.0/22 | No route object for it. A route object for 157.250.0.0/18 with origin AS53306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53306 in the RIR database for the space. |
| ROA: none | 157.250.12.0/23 | No ROA covers it. Add a ROA for AS53306, maxLength 23. |
| Route object: none | 157.250.12.0/23 | No route object for it. A route object for 157.250.0.0/18 with origin AS53306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53306 in the RIR database for the space. |
| ROA: none | 157.250.14.0/23 | No ROA covers it. Add a ROA for AS53306, maxLength 23. |
| Route object: none | 157.250.14.0/23 | No route object for it. A route object for 157.250.0.0/18 with origin AS53306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53306 in the RIR database for the space. |
| ROA: none | 157.250.16.0/20 | No ROA covers it. Add a ROA for AS53306, maxLength 20. |
| Route object: none | 157.250.16.0/20 | No route object for it. A route object for 157.250.0.0/18 with origin AS53306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53306 in the RIR database for the space. |
| ROA: none | 157.250.32.0/19 | No ROA covers it. Add a ROA for AS53306, maxLength 19. |
| Route object: none | 157.250.32.0/19 | No route object for it. A route object for 157.250.0.0/18 with origin AS53306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53306 in the RIR database for the space. |
| ROA: none | 157.250.63.0/24 | No ROA covers it. Add a ROA for AS53306, maxLength 24. |
| Route object: none | 157.250.63.0/24 | No route object for it. A route object for 157.250.0.0/18 with origin AS53306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53306 in the RIR database for the space. |
| ROA: none | 199.244.92.0/23 | No ROA covers it. Add a ROA for AS53306, maxLength 23. |
| Route object: none | 199.244.92.0/23 | No route object for it. A route object for 199.244.92.0/22 with origin AS53306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53306 in the RIR database for the space. |
| ROA: none | 216.168.192.0/19 | No ROA covers it. Add a ROA for AS53306, maxLength 19. |
Route objects not announced
Route objects with origin AS53306 whose prefix no peer sees AS53306 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 157.250.0.0/18 | ARIN | No ROA |
| 199.244.92.0/22 | ARIN | No ROA |
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.