Network · data from 2026-11-12
AS399282 CONNEXT-BROADBAND - Connext LLC
Registry name: CONNEXT-BROADBAND - Connext LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399282, 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.
| 2606:9140::/32 | No ROA | None | 631 99% |
| 162.210.21.0/24 | Valid | Nonecovered by 162.210.20.0/22 | 672 100% |
| 162.210.22.0/24 | Valid | Nonecovered by 162.210.20.0/22 | 672 100% |
| 162.210.23.0/24 | Valid | Nonecovered by 162.210.20.0/22 | 672 100% |
| 162.210.20.0/24 | Valid | Nonecovered by 162.210.20.0/22 | 671 100% |
| 209.147.105.0/24 | Valid | Nonecovered by 209.147.104.0/21 | 671 100% |
| 209.147.106.0/24 | Valid | Nonecovered by 209.147.104.0/21 | 671 100% |
| 209.147.107.0/24 | Valid | Nonecovered by 209.147.104.0/21 | 671 100% |
| 209.147.110.0/24 | Valid | Nonecovered by 209.147.104.0/21 | 671 100% |
| 209.147.108.0/24 | Valid | Nonecovered by 209.147.104.0/21 | 670 100% |
| 209.147.109.0/24 | Valid | Nonecovered by 209.147.104.0/21 | 670 100% |
| 209.147.104.0/24 | Valid | Nonecovered by 209.147.104.0/21 | 2 0%low visibility |
| 209.147.111.0/24 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS399282 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 18 are in fix.csv.
- ROA: none1
- Route object: none12
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2606:9140::/32 | No ROA covers it. Add a ROA for AS399282, maxLength 32. |
| Route object: none | 2606:9140::/32 | No route object for it. Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 162.210.21.0/24 | No route object for it. A route object for 162.210.20.0/22 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 162.210.22.0/24 | No route object for it. A route object for 162.210.20.0/22 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 162.210.23.0/24 | No route object for it. A route object for 162.210.20.0/22 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 162.210.20.0/24 | No route object for it. A route object for 162.210.20.0/22 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 209.147.105.0/24 | No route object for it. A route object for 209.147.104.0/21 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 209.147.106.0/24 | No route object for it. A route object for 209.147.104.0/21 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 209.147.107.0/24 | No route object for it. A route object for 209.147.104.0/21 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 209.147.110.0/24 | No route object for it. A route object for 209.147.104.0/21 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 209.147.108.0/24 | No route object for it. A route object for 209.147.104.0/21 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 209.147.109.0/24 | No route object for it. A route object for 209.147.104.0/21 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: none | 209.147.104.0/24 | No route object for it. A route object for 209.147.104.0/21 with origin AS399282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399282 in the RIR database for the space. |
| Route object: RIR | 209.147.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399282 whose prefix no peer sees AS399282 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.210.20.0/22 | ARIN | Valid |
| 192.200.24.0/21 | ARIN | Valid |
| 209.147.104.0/21 | ARIN | Valid |
| 2001:470:336::/48 | 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.