Network · data from 2026-11-12

AS26938 COMPUSOURCE - CompuSOURCE Communications Corp.

Registry name: COMPUSOURCE - CompuSOURCE Communications Corp., US · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 75.0% with a route object

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

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


63.69.20.0/24	Invalid: origin	Nonecovered by 63.69.16.0/21	2 0%low visibility	2
63.69.16.0/21	Invalid: origin	Other IRR onlyBBOI	2 0%low visibility	2
208.76.32.0/21	Valid	Other IRR onlyBBOI, RADB	673 100%	67
199.47.40.0/21	Valid	RIR databaseARIN, RADB	673 100%	67

63.69.20.0/24

Invalid: origin

Nonecovered by 63.69.16.0/21

2 0%low visibility

63.69.16.0/21

Invalid: origin

Other IRR onlyBBOI

2 0%low visibility

208.76.32.0/21

Valid

Other IRR onlyBBOI, RADB

673 100%

199.47.40.0/21

Valid

RIR databaseARIN, RADB

673 100%

AS-SET

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

ROA: origin2
Route object: none1
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	63.69.20.0/24	An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS26938 should announce it, add a ROA for AS26938.	2 of 673
Route object: none	63.69.20.0/24	No route object for it. A route object for 63.69.16.0/21 with origin AS26938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26938 in the RIR database for the space.	2 of 673
ROA: origin	63.69.16.0/21	An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS26938 should announce it, add a ROA for AS26938.	2 of 673
Route object: RIR	63.69.16.0/21	Route object only in BBOI. Add it in the RIR database for the space.	2 of 673
Route object: RIR	208.76.32.0/21	Route object only in BBOI, RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

63.69.20.0/24

An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS26938 should announce it, add a ROA for AS26938.

2 of 673

Route object: none

63.69.20.0/24

No route object for it. A route object for 63.69.16.0/21 with origin AS26938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26938 in the RIR database for the space.

2 of 673

ROA: origin

63.69.16.0/21

An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS26938 should announce it, add a ROA for AS26938.

2 of 673

Route object: RIR

63.69.16.0/21

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

2 of 673

Route object: RIR

208.76.32.0/21

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

673 of 673

Route objects not announced

Every route object with origin AS26938 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.