Network · data from 2026-11-12
AS27022 SIYEH-ASN-1 - Siyeh Corporation
Registry name: SIYEH-ASN-1 - Siyeh Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27022, 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.
| 66.81.136.0/23 | Valid | Nonecovered by 66.81.136.0/21 | 670 100% |
| 66.81.138.0/24 | Valid | Nonecovered by 66.81.136.0/21 | 670 100% |
| 66.81.140.0/23 | Valid | Nonecovered by 66.81.136.0/21 | 670 100% |
| 66.81.142.0/24 | Valid | Nonecovered by 66.81.136.0/21 | 670 100% |
| 174.34.236.0/24 | Valid | Nonecovered by 174.34.236.0/22 | 670 100% |
| 174.34.237.0/24 | Valid | Nonecovered by 174.34.236.0/22 | 670 100% |
| 66.81.136.0/21 | Valid | RIR databaseARIN | 670 100% |
| 158.62.192.0/22 | Valid | RIR databaseARIN | 670 100% |
| 162.221.178.0/23 | Valid | RIR databaseARIN | 670 100% |
| 174.34.236.0/22 | Valid | RIR databaseARIN | 670 100% |
| 216.122.108.0/22 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS27022 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 9 are in fix.csv.
- Route object: none6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 66.81.136.0/23 | No route object for it. A route object for 66.81.136.0/21 with origin AS27022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27022 in the RIR database for the space. |
| Route object: none | 66.81.138.0/24 | No route object for it. A route object for 66.81.136.0/21 with origin AS27022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27022 in the RIR database for the space. |
| Route object: none | 66.81.140.0/23 | No route object for it. A route object for 66.81.136.0/21 with origin AS27022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27022 in the RIR database for the space. |
| Route object: none | 66.81.142.0/24 | No route object for it. A route object for 66.81.136.0/21 with origin AS27022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27022 in the RIR database for the space. |
| Route object: none | 174.34.236.0/24 | No route object for it. A route object for 174.34.236.0/22 with origin AS27022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27022 in the RIR database for the space. |
| Route object: none | 174.34.237.0/24 | No route object for it. A route object for 174.34.236.0/22 with origin AS27022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27022 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27022 whose prefix no peer sees AS27022 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.210.132.0/22 | RADB | No ROA |
| 216.66.232.0/22 | RADB | No ROA |
| 216.66.236.0/22 | RADB | 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.