Network · data from 2026-11-12
AS397731 ELITEWORK-01 - EliteWork LLC
Registry name: ELITEWORK-01 - EliteWork LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS397731, 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.
| 104.238.234.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 192.126.128.0/17 | No ROA | Other IRR onlyRADB | 672 100% |
| 104.238.228.0/24 | No ROA | RIR databaseARIN, RADB | 672 100% |
| 158.120.255.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 192.206.41.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 66.245.172.0/24 | Valid | Nonecovered by 66.245.172.0/22 | 672 100% |
| 66.245.174.0/24 | Valid | Nonecovered by 66.245.172.0/22 | 672 100% |
| 66.245.175.0/24 | Valid | Nonecovered by 66.245.172.0/22 | 672 100% |
| 66.245.173.0/24 | Valid | Nonecovered by 66.245.172.0/22 | 671 100% |
| 104.225.132.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 165.140.236.0/22 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS397731 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.
- ROA: none5
- Route object: none4
- Route object: RIR3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 104.238.234.0/24 | No ROA covers it. Add a ROA for AS397731, maxLength 24. |
| Route object: RIR | 104.238.234.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.126.128.0/17 | No ROA covers it. Add a ROA for AS397731, maxLength 17. |
| Route object: RIR | 192.126.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.238.228.0/24 | No ROA covers it. Add a ROA for AS397731, maxLength 24. |
| ROA: none | 158.120.255.0/24 | No ROA covers it. Add a ROA for AS397731, maxLength 24. |
| ROA: none | 192.206.41.0/24 | No ROA covers it. Add a ROA for AS397731, maxLength 24. |
| Route object: none | 66.245.172.0/24 | No route object for it. A route object for 66.245.172.0/22 with origin AS397731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397731 in the RIR database for the space. |
| Route object: none | 66.245.174.0/24 | No route object for it. A route object for 66.245.172.0/22 with origin AS397731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397731 in the RIR database for the space. |
| Route object: none | 66.245.175.0/24 | No route object for it. A route object for 66.245.172.0/22 with origin AS397731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397731 in the RIR database for the space. |
| Route object: none | 66.245.173.0/24 | No route object for it. A route object for 66.245.172.0/22 with origin AS397731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397731 in the RIR database for the space. |
| Route object: RIR | 104.225.132.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS397731 whose prefix no peer sees AS397731 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.245.172.0/22 | 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.