Announced routes
Every prefix a peer of the route collectors sees with origin AS40092, 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.
| 199.204.250.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 66.84.21.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 66.84.23.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 216.222.194.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 216.222.195.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 45.56.216.0/21 | Valid | RIR databaseARIN | 673 100% |
| 194.146.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.146.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 208.79.216.0/22 | Valid | RIR databaseARIN | 673 100% |
| 216.222.192.0/23 | Valid | RIR databaseARIN | 673 100% |
| 216.222.196.0/22 | Valid | RIR databaseARIN | 673 100% |
| 216.222.200.0/23 | Valid | RIR databaseARIN | 673 100% |
| 190.180.144.0/22 | Valid | RIR databaseARIN | 672 100% |
| 194.146.116.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 200.69.0.0/21 | Valid | RIR databaseARIN | 672 100% |
| 200.69.16.0/22 | Valid | RIR databaseARIN | 672 100% |
| 208.68.104.0/22 | Valid | RIR databaseARIN | 672 100% |
| 45.114.224.0/22 | Valid | RIR databaseARIN | 671 100% |
| 172.96.176.0/22 | Valid | RIR databaseARIN | 671 100% |
| 216.7.88.0/22 | Valid | RIR databaseARIN | 671 100% |
| 66.102.128.0/20 | Valid | RIR databaseARIN | 670 100% |
| 103.26.140.0/22 | Valid | RIR databaseARIN | 668 99% |
| 2604:9780::/32 | Valid | RIR databaseARIN | 634 100% |
| 2605:6f00::/32 | Valid | RIR databaseARIN | 634 100% |
| 2620:b:e000::/48 | Valid | RIR databaseARIN | 634 100% |
| 2605:6f07::/32 | Valid | RIR databaseARIN | 633 100% |
| 2605:6f03::/32 | Valid | RIR databaseARIN | 605 95% |
| 2606:bd00::/32 | Valid | RIR databaseARIN | 605 95% |
AS-SET
AS40092'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: none5
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.204.250.0/24 | No ROA covers it. Add a ROA for AS40092, maxLength 24. |
| ROA: none | 66.84.21.0/24 | No ROA covers it. Add a ROA for AS40092, maxLength 24. |
| ROA: none | 66.84.23.0/24 | No ROA covers it. Add a ROA for AS40092, maxLength 24. |
| ROA: none | 216.222.194.0/24 | No ROA covers it. Add a ROA for AS40092, maxLength 24. |
| ROA: none | 216.222.195.0/24 | No ROA covers it. Add a ROA for AS40092, maxLength 24. |
Route objects not announced
Route objects with origin AS40092 whose prefix no peer sees AS40092 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.56.216.0/22 | ARIN | Valid |
| 45.56.220.0/22 | ARIN | Valid |
| 190.180.144.0/24 | ARIN, RADB | Valid |
| 190.180.145.0/24 | ARIN | Valid |
| 190.180.146.0/24 | ARIN | Valid |
| 190.180.147.0/24 | ARIN | Valid |
| 199.204.249.0/24 | ARIN | No ROA |
| 199.204.250.0/23 | ARIN | No ROA |
| 199.204.252.0/22 | ARIN | No ROA |
| 216.222.194.0/23 | 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.