bgpreport

Network · data from 2026-11-12

AS399282 CONNEXT-BROADBAND - Connext LLC

Registry name: CONNEXT-BROADBAND - Connext LLC, US · not in PeeringDB

12IPv4 routes 100.0% RPKI valid · 8.3% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 12 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS399282, seen from no peer

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% 68
162.210.21.0/24 Valid Nonecovered by 162.210.20.0/22 672 100% 67
162.210.22.0/24 Valid Nonecovered by 162.210.20.0/22 672 100% 67
162.210.23.0/24 Valid Nonecovered by 162.210.20.0/22 672 100% 67
162.210.20.0/24 Valid Nonecovered by 162.210.20.0/22 671 100% 69
209.147.105.0/24 Valid Nonecovered by 209.147.104.0/21 671 100% 69
209.147.106.0/24 Valid Nonecovered by 209.147.104.0/21 671 100% 69
209.147.107.0/24 Valid Nonecovered by 209.147.104.0/21 671 100% 69
209.147.110.0/24 Valid Nonecovered by 209.147.104.0/21 671 100% 69
209.147.108.0/24 Valid Nonecovered by 209.147.104.0/21 670 100% 68
209.147.109.0/24 Valid Nonecovered by 209.147.104.0/21 670 100% 68
209.147.104.0/24 Valid Nonecovered by 209.147.104.0/21 2 0%low visibility 3
209.147.111.0/24 Valid Other IRR onlyRADB 671 100% 69

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
ChangePrefix or setDetailFull-table peers
ROA: none2606:9140::/32No ROA covers it. Add a ROA for AS399282, maxLength 32.631 of 636
Route object: none2606:9140::/32No route object for it. Add a route object with origin AS399282 in the RIR database for the space.631 of 636
Route object: none162.210.21.0/24No 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.672 of 673
Route object: none162.210.22.0/24No 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.672 of 673
Route object: none162.210.23.0/24No 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.672 of 673
Route object: none162.210.20.0/24No 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.671 of 673
Route object: none209.147.105.0/24No 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.671 of 673
Route object: none209.147.106.0/24No 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.671 of 673
Route object: none209.147.107.0/24No 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.671 of 673
Route object: none209.147.110.0/24No 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.671 of 673
Route object: none209.147.108.0/24No 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.670 of 673
Route object: none209.147.109.0/24No 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.670 of 673
Route object: none209.147.104.0/24No 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.2 of 673
Route object: RIR209.147.111.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

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/22ARINValid
192.200.24.0/21ARINValid
209.147.104.0/21ARINValid
2001:470:336::/48ARINValid

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.