bgpreport

Network · data from 2026-11-12

AS2269 FR-U-PARISSUD-ORSAY - Renater

Registry name: FR-U-PARISSUD-ORSAY - Renater, EU · not in PeeringDB

14IPv4 routes 7.1% RPKI valid · 28.6% with a route object
0IPv6 routes
7RPKI invalid 0 origin · 7 maxLength
6No ROA 10 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS2269, seen from no peer

Announced routes

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

138.195.0.0/18 Invalid: maxLength Nonecovered by 138.195.0.0/16 1 0%low visibility 1
138.195.3.0/24 Invalid: maxLength Nonecovered by 138.195.0.0/16 1 0%low visibility 1
138.195.20.0/22 Invalid: maxLength Nonecovered by 138.195.0.0/16 1 0%low visibility 1
138.195.64.0/18 Invalid: maxLength Nonecovered by 138.195.0.0/16 1 0%low visibility 1
138.195.128.0/20 Invalid: maxLength Nonecovered by 138.195.0.0/16 1 0%low visibility 1
138.195.160.0/19 Invalid: maxLength Nonecovered by 138.195.0.0/16 1 0%low visibility 1
138.195.192.0/18 Invalid: maxLength Nonecovered by 138.195.0.0/16 1 0%low visibility 1
192.93.3.0/24 No ROA None 250 37% 56
192.93.157.0/24 No ROA None 250 37% 56
192.54.164.0/24 No ROA None 249 37% 56
129.175.0.0/16 No ROA RIR databaseRIPE 672 100% 68
192.44.78.0/24 No ROA RIR databaseRIPE 670 100% 68
192.70.36.0/24 No ROA RIR databaseRIPE 670 100% 68
138.231.0.0/16 Valid RIR databaseRIPE 670 100% 68

AS-SET

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

  • ROA: maxLength7
  • ROA: none6
  • Route object: none10
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength138.195.0.0/18ROA 138.195.0.0/16 AS2269 has maxLength 16; the route is a /18. Raise the maxLength, or add a ROA for 138.195.0.0/18.1 of 673
Route object: none138.195.0.0/18No route object for it. A route object for 138.195.0.0/16 with origin AS2269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2269 in the RIR database for the space.1 of 673
ROA: maxLength138.195.3.0/24ROA 138.195.0.0/16 AS2269 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 138.195.3.0/24.1 of 673
Route object: none138.195.3.0/24No route object for it. A route object for 138.195.0.0/16 with origin AS2269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2269 in the RIR database for the space.1 of 673
ROA: maxLength138.195.20.0/22ROA 138.195.0.0/16 AS2269 has maxLength 16; the route is a /22. Raise the maxLength, or add a ROA for 138.195.20.0/22.1 of 673
Route object: none138.195.20.0/22No route object for it. A route object for 138.195.0.0/16 with origin AS2269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2269 in the RIR database for the space.1 of 673
ROA: maxLength138.195.64.0/18ROA 138.195.0.0/16 AS2269 has maxLength 16; the route is a /18. Raise the maxLength, or add a ROA for 138.195.64.0/18.1 of 673
Route object: none138.195.64.0/18No route object for it. A route object for 138.195.0.0/16 with origin AS2269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2269 in the RIR database for the space.1 of 673
ROA: maxLength138.195.128.0/20ROA 138.195.0.0/16 AS2269 has maxLength 16; the route is a /20. Raise the maxLength, or add a ROA for 138.195.128.0/20.1 of 673
Route object: none138.195.128.0/20No route object for it. A route object for 138.195.0.0/16 with origin AS2269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2269 in the RIR database for the space.1 of 673
ROA: maxLength138.195.160.0/19ROA 138.195.0.0/16 AS2269 has maxLength 16; the route is a /19. Raise the maxLength, or add a ROA for 138.195.160.0/19.1 of 673
Route object: none138.195.160.0/19No route object for it. A route object for 138.195.0.0/16 with origin AS2269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2269 in the RIR database for the space.1 of 673
ROA: maxLength138.195.192.0/18ROA 138.195.0.0/16 AS2269 has maxLength 16; the route is a /18. Raise the maxLength, or add a ROA for 138.195.192.0/18.1 of 673
Route object: none138.195.192.0/18No route object for it. A route object for 138.195.0.0/16 with origin AS2269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2269 in the RIR database for the space.1 of 673
ROA: none192.93.3.0/24No ROA covers it. Add a ROA for AS2269, maxLength 24.250 of 673
Route object: none192.93.3.0/24No route object for it. Add a route object with origin AS2269 in the RIR database for the space.250 of 673
ROA: none192.93.157.0/24No ROA covers it. Add a ROA for AS2269, maxLength 24.250 of 673
Route object: none192.93.157.0/24No route object for it. Add a route object with origin AS2269 in the RIR database for the space.250 of 673
ROA: none192.54.164.0/24No ROA covers it. Add a ROA for AS2269, maxLength 24.249 of 673
Route object: none192.54.164.0/24No route object for it. Add a route object with origin AS2269 in the RIR database for the space.249 of 673
ROA: none129.175.0.0/16No ROA covers it. Add a ROA for AS2269, maxLength 16.672 of 673
ROA: none192.44.78.0/24No ROA covers it. Add a ROA for AS2269, maxLength 24.670 of 673
ROA: none192.70.36.0/24No ROA covers it. Add a ROA for AS2269, maxLength 24.670 of 673

Route objects not announced

Route objects with origin AS2269 whose prefix no peer sees AS2269 announce. Many are kept on purpose (backup routes, space announced only in some places).

138.195.0.0/16RIPEValid

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.