Network · data from 2026-11-12
AS22027 CBTS-USONX-01 - CBTS Technology Solutions LLC
Registry name: CBTS-USONX-01 - CBTS Technology Solutions LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22027, 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.240.132.0/24 | No ROA | None | 672 100% |
| 66.240.133.0/24 | No ROA | None | 672 100% |
| 66.240.134.0/24 | No ROA | Nonecovered by 66.240.134.0/23 | 671 100% |
| 66.240.135.0/24 | No ROA | Nonecovered by 66.240.134.0/23 | 671 100% |
| 206.82.144.0/22 | Valid | Nonecovered by 206.82.144.0/20 | 673 100% |
| 206.82.149.0/24 | Valid | Nonecovered by 206.82.144.0/20 | 673 100% |
| 206.82.152.0/21 | Valid | Nonecovered by 206.82.144.0/20 | 673 100% |
| 206.82.148.0/24 | Valid | Other IRR onlyALTDB | 673 100% |
AS-SET
AS22027 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: none4
- Route object: none7
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.240.132.0/24 | No ROA covers it. Add a ROA for AS22027, maxLength 24. |
| Route object: none | 66.240.132.0/24 | No route object for it. Add a route object with origin AS22027 in the RIR database for the space. |
| ROA: none | 66.240.133.0/24 | No ROA covers it. Add a ROA for AS22027, maxLength 24. |
| Route object: none | 66.240.133.0/24 | No route object for it. Add a route object with origin AS22027 in the RIR database for the space. |
| ROA: none | 66.240.134.0/24 | No ROA covers it. Add a ROA for AS22027, maxLength 24. |
| Route object: none | 66.240.134.0/24 | No route object for it. A route object for 66.240.134.0/23 with origin AS22027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22027 in the RIR database for the space. |
| ROA: none | 66.240.135.0/24 | No ROA covers it. Add a ROA for AS22027, maxLength 24. |
| Route object: none | 66.240.135.0/24 | No route object for it. A route object for 66.240.134.0/23 with origin AS22027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22027 in the RIR database for the space. |
| Route object: none | 206.82.144.0/22 | No route object for it. A route object for 206.82.144.0/20 with origin AS22027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22027 in the RIR database for the space. |
| Route object: none | 206.82.149.0/24 | No route object for it. A route object for 206.82.144.0/20 with origin AS22027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22027 in the RIR database for the space. |
| Route object: none | 206.82.152.0/21 | No route object for it. A route object for 206.82.144.0/20 with origin AS22027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22027 in the RIR database for the space. |
| Route object: RIR | 206.82.148.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22027 whose prefix no peer sees AS22027 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.240.134.0/23 | ALTDB | No ROA |
| 206.82.144.0/20 | 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.