Announced routes
Every prefix a peer of the route collectors sees with origin AS202448, 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.
| 45.137.149.0/24 | Valid | Nonecovered by 45.137.148.0/22 | 672 100% |
| 45.137.150.0/24 | Valid | Nonecovered by 45.137.148.0/22 | 672 100% |
| 45.137.151.0/24 | Valid | Nonecovered by 45.137.148.0/22 | 671 100% |
| 45.137.148.0/24 | Valid | Nonecovered by 45.137.148.0/22 | 670 100% |
| 2a0c:b9c0::/32 | Valid | Nonecovered by 2a0c:b9c0::/29 | 631 99% |
| 2.56.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2.56.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2.56.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2.56.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.238.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.222.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 62.3.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.137.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.137.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.137.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.137.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.137.174.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.105.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.106.181.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.107.197.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.250.248.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.250.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.114.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.16.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.17.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.18.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.22.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.23.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.169.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.157.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.157.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.96.163.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.177.73.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.234.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.243.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.243.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.212.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.212.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.24.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.24.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.24.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.24.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.201.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.26.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.76.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.78.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.99.23.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.153.184.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.153.186.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.153.187.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.137.175.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 93.114.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.157.82.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.215.237.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.170.215.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.63.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.14.9.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.153.185.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.238.132.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.38.128.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.38.135.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.43.33.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.227.40.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.227.41.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.236.195.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.115.19.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.176.182.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.231.205.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.169.201.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.169.204.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.169.205.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.32.77.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.32.79.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.99.20.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.99.21.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.99.22.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a09:cd42::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a09:cd43::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a09:cd44::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a09:cd45::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:b9c1::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a09:cd40::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a09:cd46::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a09:cd41::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:8280::/32 | Valid | RIR databaseRIPE | 628 99% |
AS-SET
AS202448'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 21 are in fix.csv.
- Route object: none5
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.137.149.0/24 | No route object for it. A route object for 45.137.148.0/22 with origin AS202448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202448 in the RIR database for the space. |
| Route object: none | 45.137.150.0/24 | No route object for it. A route object for 45.137.148.0/22 with origin AS202448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202448 in the RIR database for the space. |
| Route object: none | 45.137.151.0/24 | No route object for it. A route object for 45.137.148.0/22 with origin AS202448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202448 in the RIR database for the space. |
| Route object: none | 45.137.148.0/24 | No route object for it. A route object for 45.137.148.0/22 with origin AS202448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202448 in the RIR database for the space. |
| Route object: none | 2a0c:b9c0::/32 | No route object for it. A route object for 2a0c:b9c0::/29 with origin AS202448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202448 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202448 whose prefix no peer sees AS202448 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.137.148.0/22 | RIPE | No ROA |
| 85.137.20.0/22 | RIPE | Valid |
| 85.137.20.0/24 | RIPE | Valid |
| 85.137.21.0/24 | RIPE | Valid |
| 85.137.22.0/24 | RIPE | Valid |
| 85.137.23.0/24 | RIPE | Valid |
| 85.137.168.0/24 | RIPE | Valid |
| 85.137.169.0/24 | RIPE | Valid |
| 85.137.170.0/23 | RIPE | No ROA |
| 85.137.174.0/23 | RIPE | No ROA |
| 91.250.248.0/23 | RIPE | No ROA |
| 185.170.212.0/22 | RIPE | No ROA |
| 193.24.232.0/22 | RIPE | No ROA |
| 194.32.76.0/22 | RIPE | No ROA |
| 2a09:cd47::/32 | RIPE | No ROA |
| 2a0c:b9c0::/29 | 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.