Network · data from 2026-11-12
AS64294 PAC-GCS - Panasonic Avionics Corporation
Registry name: PAC-GCS - Panasonic Avionics Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS64294, 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.21.160.0/23 | No ROA | None | 673 100% |
| 199.21.160.0/24 | No ROA | None | 673 100% |
| 199.21.161.0/24 | No ROA | None | 673 100% |
| 199.21.162.0/24 | No ROA | Other origin only | 673 100% |
| 103.242.88.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 205.220.134.0/24 | Valid | Nonecovered by 205.220.128.0/19 | 673 100% |
| 205.220.128.0/23 | Valid | RIR databaseARIN | 673 100% |
| 205.220.130.0/23 | Valid | RIR databaseARIN | 673 100% |
| 205.220.130.0/24 | Valid | RIR databaseARIN | 673 100% |
| 205.220.136.0/23 | Valid | RIR databaseARIN | 673 100% |
| 205.220.148.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 205.220.132.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 205.220.138.0/23 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS64294 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 14 are in fix.csv.
- ROA: none5
- Route object: none5
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.21.160.0/23 | No ROA covers it. Add a ROA for AS64294, maxLength 23. |
| Route object: none | 199.21.160.0/23 | No route object for it. Add a route object with origin AS64294 in the RIR database for the space. |
| ROA: none | 199.21.160.0/24 | No ROA covers it. Add a ROA for AS64294, maxLength 24. |
| Route object: none | 199.21.160.0/24 | No route object for it. Add a route object with origin AS64294 in the RIR database for the space. |
| ROA: none | 199.21.161.0/24 | No ROA covers it. Add a ROA for AS64294, maxLength 24. |
| Route object: none | 199.21.161.0/24 | No route object for it. Add a route object with origin AS64294 in the RIR database for the space. |
| ROA: none | 199.21.162.0/24 | No ROA covers it. Add a ROA for AS64294, maxLength 24. |
| Route object: none | 199.21.162.0/24 | Route objects for it name AS39996. Add a route object with origin AS64294 in the RIR database for the space. |
| ROA: none | 103.242.88.0/23 | No ROA covers it. Add a ROA for AS64294, maxLength 23. |
| Route object: RIR | 103.242.88.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 205.220.134.0/24 | No route object for it. A route object for 205.220.128.0/19 with origin AS64294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64294 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS64294 whose prefix no peer sees AS64294 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 205.220.128.0/19 | ARIN | Valid |
| 205.220.138.0/24 | ARIN | Valid |
| 205.220.139.0/24 | ARIN | 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.