Network · data from 2026-11-12
AS14410 HYETECH - Hye Tech Network & Security Solutions, LLC
Registry name: HYETECH - Hye Tech Network & Security Solutions, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14410, 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.222.0.0/21 | No ROA | Nonecovered by 104.222.0.0/20 | 673 100% |
| 104.222.8.0/21 | No ROA | Nonecovered by 104.222.0.0/20 | 673 100% |
| 199.101.203.0/24 | No ROA | Nonecovered by 199.101.200.0/22 | 673 100% |
| 199.101.200.0/24 | No ROA | Nonecovered by 199.101.200.0/22 | 670 100% |
| 199.101.201.0/24 | No ROA | Nonecovered by 199.101.200.0/22 | 670 100% |
| 199.101.202.0/24 | No ROA | Nonecovered by 199.101.200.0/22 | 670 100% |
| 199.101.200.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 104.222.0.0/20 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 2620:3d:a000::/48 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
AS14410 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 17 are in fix.csv.
- ROA: none9
- Route object: none6
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 104.222.0.0/21 | No ROA covers it. Add a ROA for AS14410, maxLength 21. |
| Route object: none | 104.222.0.0/21 | No route object for it. A route object for 104.222.0.0/20 with origin AS14410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14410 in the RIR database for the space. |
| ROA: none | 104.222.8.0/21 | No ROA covers it. Add a ROA for AS14410, maxLength 21. |
| Route object: none | 104.222.8.0/21 | No route object for it. A route object for 104.222.0.0/20 with origin AS14410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14410 in the RIR database for the space. |
| ROA: none | 199.101.203.0/24 | No ROA covers it. Add a ROA for AS14410, maxLength 24. |
| Route object: none | 199.101.203.0/24 | No route object for it. A route object for 199.101.200.0/22 with origin AS14410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14410 in the RIR database for the space. |
| ROA: none | 199.101.200.0/24 | No ROA covers it. Add a ROA for AS14410, maxLength 24. |
| Route object: none | 199.101.200.0/24 | No route object for it. A route object for 199.101.200.0/22 with origin AS14410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14410 in the RIR database for the space. |
| ROA: none | 199.101.201.0/24 | No ROA covers it. Add a ROA for AS14410, maxLength 24. |
| Route object: none | 199.101.201.0/24 | No route object for it. A route object for 199.101.200.0/22 with origin AS14410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14410 in the RIR database for the space. |
| ROA: none | 199.101.202.0/24 | No ROA covers it. Add a ROA for AS14410, maxLength 24. |
| Route object: none | 199.101.202.0/24 | No route object for it. A route object for 199.101.200.0/22 with origin AS14410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14410 in the RIR database for the space. |
| ROA: none | 199.101.200.0/22 | No ROA covers it. Add a ROA for AS14410, maxLength 22. |
| Route object: RIR | 199.101.200.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.222.0.0/20 | No ROA covers it. Add a ROA for AS14410, maxLength 20. |
| ROA: none | 2620:3d:a000::/48 | No ROA covers it. Add a ROA for AS14410, maxLength 48. |
Route objects not announced
Route objects with origin AS14410 whose prefix no peer sees AS14410 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 169.150.112.0/20 | 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.