Announced routes
Every prefix a peer of the route collectors sees with origin AS57168, 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.
| 185.3.166.0/24 | No ROA | Nonecovered by 185.3.164.0/22 | 2 0%low visibility |
| 5.44.232.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 109.235.151.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.96.64.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.96.65.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.96.66.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 5.44.238.0/24 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 109.235.146.0/23 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 109.235.148.0/24 | No ROA | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS57168'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 38 are in fix.csv.
- ROA: none9
- Route object: none1
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.3.166.0/24 | No ROA covers it. Add a ROA for AS57168, maxLength 24. |
| Route object: none | 185.3.166.0/24 | No route object for it. A route object for 185.3.164.0/22 with origin AS57168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57168 in the RIR database for the space. |
| ROA: none | 5.44.232.0/22 | No ROA covers it. Add a ROA for AS57168, maxLength 22. |
| ROA: none | 109.235.151.0/24 | No ROA covers it. Add a ROA for AS57168, maxLength 24. |
| ROA: none | 185.96.64.0/24 | No ROA covers it. Add a ROA for AS57168, maxLength 24. |
| ROA: none | 185.96.65.0/24 | No ROA covers it. Add a ROA for AS57168, maxLength 24. |
| ROA: none | 185.96.66.0/23 | No ROA covers it. Add a ROA for AS57168, maxLength 23. |
| ROA: none | 5.44.238.0/24 | No ROA covers it. Add a ROA for AS57168, maxLength 24. |
| ROA: none | 109.235.146.0/23 | No ROA covers it. Add a ROA for AS57168, maxLength 23. |
| ROA: none | 109.235.148.0/24 | No ROA covers it. Add a ROA for AS57168, maxLength 24. |
Route objects not announced
Route objects with origin AS57168 whose prefix no peer sees AS57168 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.44.232.0/21 | RIPE | No ROA |
| 5.44.232.0/24 | RIPE | No ROA |
| 5.44.233.0/24 | RIPE | No ROA |
| 5.44.236.0/23 | RIPE | No ROA |
| 5.44.236.0/24 | RIPE | No ROA |
| 5.44.237.0/24 | RADB, RIPE | No ROA |
| 5.44.239.0/24 | RIPE | No ROA |
| 46.236.56.0/24 | RIPE | Invalid: origin |
| 46.236.60.0/24 | RIPE | Invalid: origin |
| 89.150.51.0/24 | RIPE | No ROA |
| 91.232.148.0/23 | RIPE | No ROA |
| 109.235.144.0/21 | RIPE | No ROA |
| 109.235.144.0/22 | RIPE | No ROA |
| 109.235.144.0/24 | RIPE | No ROA |
| 109.235.145.0/24 | RIPE | No ROA |
| 109.235.147.0/24 | RIPE | No ROA |
| 109.235.148.0/23 | RIPE | No ROA |
| 109.235.149.0/24 | RIPE | No ROA |
| 109.235.150.0/24 | RADB, RIPE | No ROA |
| 185.3.164.0/22 | RIPE | No ROA |
| 185.3.167.0/24 | RIPE | No ROA |
| 185.77.152.0/23 | RIPE | No ROA |
| 185.96.60.0/22 | RIPE | No ROA |
| 185.96.61.0/24 | RIPE | No ROA |
| 185.96.64.0/22 | RIPE | No ROA |
| 185.96.64.0/23 | RIPE | No ROA |
| 185.96.66.0/24 | RIPE | No ROA |
| 185.96.67.0/24 | RIPE | 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.