Announced routes
Every prefix a peer of the route collectors sees with origin AS394434, 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.
| 38.99.4.0/24 | No ROA | None | 2 0%low visibility |
| 64.65.26.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 159.183.255.0/24 | Valid | Nonecovered by 159.183.254.0/23 | 673 100% |
| 168.86.175.0/24 | Valid | None | 673 100% |
| 159.183.252.0/24 | Valid | Nonecovered by 159.183.252.0/23 | 672 100% |
| 159.183.254.0/24 | Valid | Nonecovered by 159.183.254.0/23 | 672 100% |
| 67.213.136.0/23 | Valid | RIR databaseARIN | 673 100% |
| 103.36.110.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.36.111.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.75.151.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.144.142.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.146.214.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 159.26.160.0/24 | Valid | RIR databaseARIN | 673 100% |
| 159.26.162.0/24 | Valid | RIR databaseARIN | 673 100% |
| 159.26.164.0/24 | Valid | RIR databaseARIN | 673 100% |
| 159.26.166.0/24 | Valid | RIR databaseARIN | 673 100% |
| 159.26.170.0/24 | Valid | RIR databaseARIN | 673 100% |
| 159.26.172.0/24 | Valid | RIR databaseARIN | 673 100% |
| 159.26.173.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.160.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.161.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.162.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.163.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.164.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.165.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.166.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.167.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.168.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.169.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.170.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.171.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.172.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.173.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.174.0/24 | Valid | RIR databaseARIN | 673 100% |
| 168.86.177.0/24 | Valid | RIR databaseARIN | 673 100% |
| 185.187.132.0/23 | Valid | RIR databaseNTTCOM, RIPE | 673 100% |
| 185.187.132.0/24 | Valid | RIR databaseNTTCOM, RIPE | 673 100% |
| 185.194.136.0/23 | Valid | RIR databaseNTTCOM, RIPE | 673 100% |
| 208.78.112.0/22 | Valid | RIR databaseARIN | 673 100% |
| 208.78.112.0/23 | Valid | RIR databaseARIN | 673 100% |
| 208.78.114.0/24 | Valid | RIR databaseARIN | 673 100% |
| 159.26.161.0/24 | Valid | RIR databaseARIN | 672 100% |
| 159.183.250.0/24 | Valid | RIR databaseARIN | 672 100% |
| 159.183.253.0/24 | Valid | RIR databaseARIN | 672 100% |
| 168.86.176.0/24 | Valid | RIR databaseARIN | 668 99% |
AS-SET
AS394434'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 40 are in fix.csv.
- ROA: none2
- Route object: none5
- Route object: not announced33
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.99.4.0/24 | No ROA covers it. Add a ROA for AS394434, maxLength 24. |
| Route object: none | 38.99.4.0/24 | No route object for it. Add a route object with origin AS394434 in the RIR database for the space. |
| ROA: none | 64.65.26.0/24 | No ROA covers it. Add a ROA for AS394434, maxLength 24. |
| Route object: none | 159.183.255.0/24 | No route object for it. A route object for 159.183.254.0/23 with origin AS394434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394434 in the RIR database for the space. |
| Route object: none | 168.86.175.0/24 | No route object for it. Add a route object with origin AS394434 in the RIR database for the space. |
| Route object: none | 159.183.252.0/24 | No route object for it. A route object for 159.183.252.0/23 with origin AS394434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394434 in the RIR database for the space. |
| Route object: none | 159.183.254.0/24 | No route object for it. A route object for 159.183.254.0/23 with origin AS394434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394434 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394434 whose prefix no peer sees AS394434 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.213.136.0/22 | ARIN | Valid |
| 67.213.136.0/24 | ARIN | Valid |
| 67.213.137.0/24 | ARIN | Valid |
| 67.213.138.0/23 | ARIN | Valid |
| 67.213.138.0/24 | ARIN | Valid |
| 67.213.139.0/24 | ARIN | Valid |
| 103.36.108.0/22 | APNIC | Valid |
| 159.26.163.0/24 | ARIN | Valid |
| 159.26.165.0/24 | ARIN | Valid |
| 159.26.167.0/24 | ARIN | Valid |
| 159.26.168.0/24 | ARIN | Valid |
| 159.26.169.0/24 | ARIN | Valid |
| 159.26.171.0/24 | ARIN | Valid |
| 159.26.174.0/24 | ARIN | Valid |
| 159.26.175.0/24 | ARIN | Valid |
| 159.183.252.0/22 | ARIN | Valid |
| 159.183.252.0/23 | ARIN | Valid |
| 159.183.254.0/23 | ARIN | Valid |
| 185.187.132.0/22 | NTTCOM | No ROA |
| 185.187.133.0/24 | RIPE | Valid |
| 185.187.134.0/23 | NTTCOM, RIPE | Valid |
| 185.187.134.0/24 | RIPE | Valid |
| 185.187.135.0/24 | RIPE | Valid |
| 185.194.136.0/22 | NTTCOM | No ROA |
| 185.194.136.0/24 | NTTCOM, RIPE | Valid |
| 185.194.137.0/24 | NTTCOM, RIPE | Valid |
| 185.194.138.0/23 | RIPE | Valid |
| 185.194.138.0/24 | RIPE | Valid |
| 185.194.139.0/24 | RIPE | Valid |
| 208.78.112.0/24 | ARIN | Valid |
| 208.78.114.0/23 | ARIN | Valid |
| 208.78.115.0/24 | ARIN | Valid |
| 2a0b:a580::/32 | RIPE | Valid |
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.