Network · data from 2026-11-12

AS10 CSNET-EXT-AS - CSNET Coordination and Information Center (CSNET-CIC)

Registry name: CSNET-EXT-AS - CSNET Coordination and Information Center (CSNET-CIC), US · not in PeeringDB

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

1IPv6 routes 0.0% RPKI valid · 0.0% with a route object

2RPKI invalid 2 origin · 0 maxLength

1No ROA 3 with no route object for this origin

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

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

Announced routes

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


2001:df1:e040::/48	Invalid: origin	Other origin only	56 9%low visibility	37
141.101.225.0/24	Invalid: origin	Other origin only	5 1%low visibility	6
195.74.62.0/23	No ROA	Other origin only	37 5%low visibility	25

2001:df1:e040::/48

Invalid: origin

Other origin only

56 9%low visibility

141.101.225.0/24

Invalid: origin

Other origin only

5 1%low visibility

195.74.62.0/23

No ROA

Other origin only

37 5%low visibility

AS-SET

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

ROA: origin2
ROA: none1
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	2001:df1:e040::/48	ROAs covering it name AS150245, not AS10. If AS10 should announce it, add a ROA for AS10.	56 of 636
Route object: none	2001:df1:e040::/48	Route objects for it name AS150245. Add a route object with origin AS10 in the RIR database for the space.	56 of 636
ROA: origin	141.101.225.0/24	ROAs covering it name AS201717, not AS10. If AS10 should announce it, add a ROA for AS10.	5 of 673
Route object: none	141.101.225.0/24	Route objects for it name AS201717. Add a route object with origin AS10 in the RIR database for the space.	5 of 673
ROA: none	195.74.62.0/23	No ROA covers it. Add a ROA for AS10, maxLength 23.	37 of 673
Route object: none	195.74.62.0/23	Route objects for it name AS48527. Add a route object with origin AS10 in the RIR database for the space.	37 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

2001:df1:e040::/48

ROAs covering it name AS150245, not AS10. If AS10 should announce it, add a ROA for AS10.

56 of 636

Route object: none

2001:df1:e040::/48

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

56 of 636

ROA: origin

141.101.225.0/24

ROAs covering it name AS201717, not AS10. If AS10 should announce it, add a ROA for AS10.

5 of 673

Route object: none

141.101.225.0/24

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

5 of 673

ROA: none

195.74.62.0/23

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

37 of 673

Route object: none

195.74.62.0/23

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

37 of 673

Route objects not announced

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