Network · data from 2026-11-12
AS54381 SACATECH
Registry name: SACATECH - SACA Technologies, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54381, 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.180.73.0/24 | Valid | Nonecovered by 66.180.72.0/21 | 673 100% |
| 66.180.76.0/24 | Valid | Nonecovered by 66.180.72.0/21 | 673 100% |
| 66.180.77.0/24 | Valid | Nonecovered by 66.180.72.0/21 | 673 100% |
| 66.180.78.0/24 | Valid | Nonecovered by 66.180.72.0/21 | 673 100% |
| 66.180.79.0/24 | Valid | Nonecovered by 66.180.72.0/21 | 673 100% |
| 199.122.112.0/24 | Valid | Nonecovered by 199.122.112.0/22 | 673 100% |
| 199.122.113.0/24 | Valid | Nonecovered by 199.122.112.0/22 | 673 100% |
| 199.122.114.0/24 | Valid | Nonecovered by 199.122.112.0/22 | 673 100% |
| 66.180.75.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 199.122.115.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 66.180.72.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 198.212.38.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS54381'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 13 are in fix.csv.
- Route object: none8
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 66.180.73.0/24 | No route object for it. A route object for 66.180.72.0/21 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: none | 66.180.76.0/24 | No route object for it. A route object for 66.180.72.0/21 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: none | 66.180.77.0/24 | No route object for it. A route object for 66.180.72.0/21 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: none | 66.180.78.0/24 | No route object for it. A route object for 66.180.72.0/21 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: none | 66.180.79.0/24 | No route object for it. A route object for 66.180.72.0/21 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: none | 199.122.112.0/24 | No route object for it. A route object for 199.122.112.0/22 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: none | 199.122.113.0/24 | No route object for it. A route object for 199.122.112.0/22 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: none | 199.122.114.0/24 | No route object for it. A route object for 199.122.112.0/22 with origin AS54381 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54381 in the RIR database for the space. |
| Route object: RIR | 66.180.75.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.122.115.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54381 whose prefix no peer sees AS54381 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.180.72.0/21 | ARIN | Valid |
| 66.180.74.0/24 | RADB | Valid |
| 199.122.112.0/22 | ARIN, RADB | 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.