Network · data from 2026-11-12

AS397686 C1CX-TX - C1CX

Registry name: C1CX-TX - C1CX, US · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 0.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 4 with no route object for this origin

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

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

Announced routes

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


69.174.89.0/24	No ROA	None	673 100%	67
162.142.18.0/23	No ROA	None	673 100%	67
162.142.18.0/24	No ROA	None	673 100%	67
162.142.19.0/24	No ROA	None	672 100%	67

AS-SET

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

ROA: none4
Route object: none4

Change	Prefix or set	Detail	Full-table peers
ROA: none	69.174.89.0/24	No ROA covers it. Add a ROA for AS397686, maxLength 24.	673 of 673
Route object: none	69.174.89.0/24	No route object for it. Add a route object with origin AS397686 in the RIR database for the space.	673 of 673
ROA: none	162.142.18.0/23	No ROA covers it. Add a ROA for AS397686, maxLength 23.	673 of 673
Route object: none	162.142.18.0/23	No route object for it. Add a route object with origin AS397686 in the RIR database for the space.	673 of 673
ROA: none	162.142.18.0/24	No ROA covers it. Add a ROA for AS397686, maxLength 24.	673 of 673
Route object: none	162.142.18.0/24	No route object for it. Add a route object with origin AS397686 in the RIR database for the space.	673 of 673
ROA: none	162.142.19.0/24	No ROA covers it. Add a ROA for AS397686, maxLength 24.	672 of 673
Route object: none	162.142.19.0/24	No route object for it. Add a route object with origin AS397686 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

69.174.89.0/24

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

673 of 673

Route object: none

69.174.89.0/24

No route object for it. Add a route object with origin AS397686 in the RIR database for the space.

673 of 673

ROA: none

162.142.18.0/23

No ROA covers it. Add a ROA for AS397686, maxLength 23.

673 of 673

Route object: none

162.142.18.0/23

No route object for it. Add a route object with origin AS397686 in the RIR database for the space.

673 of 673

ROA: none

162.142.18.0/24

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

673 of 673

Route object: none

162.142.18.0/24

No route object for it. Add a route object with origin AS397686 in the RIR database for the space.

673 of 673

ROA: none

162.142.19.0/24

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

672 of 673

Route object: none

162.142.19.0/24

No route object for it. Add a route object with origin AS397686 in the RIR database for the space.

672 of 673

Route objects not announced

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