Announced routes
Every prefix a peer of the route collectors sees with origin AS57608, 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.
| 84.205.168.0/24 | No ROA | Other origin only | 1 0%low visibility |
| 2a0c:2d80::/29 | No ROA | RIR databaseRIPE | 634 100% |
| 185.242.127.0/24 | Valid | Other origin only | 673 100% |
| 84.205.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.204.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.205.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.238.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.240.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.234.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.233.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.46.168.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.238.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.32.180.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.203.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.11.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.11.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.11.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.11.224.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.88.214.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.177.4.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.225.136.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.9.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.9.234.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.9.235.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 176.102.184.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 2a04:9b80::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS57608'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 15 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 84.205.168.0/24 | No ROA covers it. Add a ROA for AS57608, maxLength 24. |
| Route object: none | 84.205.168.0/24 | Route objects for it name AS206679. Add a route object with origin AS57608 in the RIR database for the space. |
| ROA: none | 2a0c:2d80::/29 | No ROA covers it. Add a ROA for AS57608, maxLength 29. |
| Route object: none | 185.242.127.0/24 | Route objects for it name AS60589. Add a route object with origin AS57608 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS57608 whose prefix no peer sees AS57608 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 84.205.161.0/24 | RIPE | No ROA |
| 185.242.127.0/32 | RIPE | Invalid: maxLength |
| 194.11.192.0/22 | RIPE | Invalid: origin |
| 194.177.4.0/23 | RIPE | Invalid: maxLength |
| 194.177.4.0/24 | RIPE | Invalid: maxLength |
| 194.177.5.0/24 | RIPE | Invalid: maxLength |
| 194.177.6.0/23 | RIPE | Invalid: maxLength |
| 194.177.6.0/24 | RIPE | Invalid: maxLength |
| 194.177.7.0/24 | RIPE | Invalid: maxLength |
| 2a0c:e7c0::/29 | RIPE | No ROA |
| 2a10:f781:10:e38::/64 | 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.