Network · data from 2026-11-12

AS401693 CANI - Brightpoint

Registry name: CANI - Brightpoint, US · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 100.0% with a route object

4IPv6 routes 50.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS401693, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS401693, 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.


2602:81b:7000::/48	No ROA	Nonecovered by 2602:81b:7000::/44	635 100%	68
204.69.246.0/24	No ROA	Other IRR onlyRADB	673 100%	67
2602:81b:7000::/44	No ROA	Other IRR onlyRADB	635 100%	68
2001:438:39::/48	Valid	Other origin only	635 100%	68
184.17.102.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
2001:1960:2a02::/48	Valid	RIR databaseARIN, RADB	635 100%	68

AS-SET

AS401693 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 7 are in fix.csv.

ROA: none3
Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	2602:81b:7000::/48	No ROA covers it. Add a ROA for AS401693, maxLength 48.	635 of 636
Route object: none	2602:81b:7000::/48	No route object for it. A route object for 2602:81b:7000::/44 with origin AS401693 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401693 in the RIR database for the space.	635 of 636
ROA: none	204.69.246.0/24	No ROA covers it. Add a ROA for AS401693, maxLength 24.	673 of 673
Route object: RIR	204.69.246.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	2602:81b:7000::/44	No ROA covers it. Add a ROA for AS401693, maxLength 44.	635 of 636
Route object: RIR	2602:81b:7000::/44	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
Route object: none	2001:438:39::/48	Route objects for it name AS17025. Add a route object with origin AS401693 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2602:81b:7000::/48

No ROA covers it. Add a ROA for AS401693, maxLength 48.

635 of 636

Route object: none

2602:81b:7000::/48

No route object for it. A route object for 2602:81b:7000::/44 with origin AS401693 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401693 in the RIR database for the space.

635 of 636

ROA: none

204.69.246.0/24

No ROA covers it. Add a ROA for AS401693, maxLength 24.

673 of 673

Route object: RIR

204.69.246.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

2602:81b:7000::/44

No ROA covers it. Add a ROA for AS401693, maxLength 44.

635 of 636

Route object: RIR

2602:81b:7000::/44

Route object only in RADB. Add it in the RIR database for the space.

635 of 636

Route object: none

2001:438:39::/48

Route objects for it name AS17025. Add a route object with origin AS401693 in the RIR database for the space.

635 of 636

Route objects not announced

Every route object with origin AS401693 is announced.

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.