Network · data from 2026-11-12
AS21748 SKYCOM1 - SKYCOM1
Registry name: SKYCOM1 - SKYCOM1, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21748, 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.37.232.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 104.37.233.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 104.37.234.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 104.37.235.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 104.37.236.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 104.37.237.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 104.37.238.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 104.37.239.0/24 | Valid | Nonecovered by 104.37.232.0/21 | 673 100% |
| 2606:8b40::/32 | Valid | RIR databaseARIN | 605 95% |
AS-SET
AS21748 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: none8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 104.37.232.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
| Route object: none | 104.37.233.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
| Route object: none | 104.37.234.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
| Route object: none | 104.37.235.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
| Route object: none | 104.37.236.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
| Route object: none | 104.37.237.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
| Route object: none | 104.37.238.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
| Route object: none | 104.37.239.0/24 | No route object for it. A route object for 104.37.232.0/21 with origin AS21748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21748 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21748 whose prefix no peer sees AS21748 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.37.232.0/21 | 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.