bgpreport

Network · data from 2026-11-12

AS31221 nLighten France

Registry name: NLT-FR nLighten France SAS, FR · PeeringDB

8IPv4 routes 12.5% RPKI valid · 62.5% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS31221, seen from no peer

Announced routes

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

5.252.57.0/24 No ROA Nonecovered by 5.252.56.0/22 673 100% 66
193.135.126.0/24 No ROA None 673 100% 67
217.13.48.0/24 No ROA Nonecovered by 217.13.48.0/21 673 100% 66
185.43.36.0/22 No ROA RIR databaseRIPE 673 100% 66
217.13.48.0/20 No ROA RIR databaseRIPE 673 100% 66
217.13.63.0/24 No ROA RIR databaseRIPE 673 100% 66
5.252.56.0/22 No ROA RIR databaseRIPE 665 99% 66
2a02:6f0::/32 No ROA RIR databaseRIPE 636 100% 69
193.218.120.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS31221: RIPE::AS-EUCLYDE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS31221 isn't in the set, or no route object for AS31221 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS31221 in itNot covered
RIPE::AS-EUCLYDE RIPE 213962 Yes 1

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

  • ROA: none8
  • Route object: none3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none5.252.57.0/24No ROA covers it. Add a ROA for AS31221, maxLength 24.673 of 673
Route object: none5.252.57.0/24No route object for it. A route object for 5.252.56.0/22 with origin AS31221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31221 in the RIR database for the space.673 of 673
ROA: none193.135.126.0/24No ROA covers it. Add a ROA for AS31221, maxLength 24.673 of 673
Route object: none193.135.126.0/24No route object for it. Add a route object with origin AS31221 in the RIR database for the space.673 of 673
ROA: none217.13.48.0/24No ROA covers it. Add a ROA for AS31221, maxLength 24.673 of 673
Route object: none217.13.48.0/24No route object for it. A route object for 217.13.48.0/21 with origin AS31221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31221 in the RIR database for the space.673 of 673
ROA: none185.43.36.0/22No ROA covers it. Add a ROA for AS31221, maxLength 22.673 of 673
ROA: none217.13.48.0/20No ROA covers it. Add a ROA for AS31221, maxLength 20.673 of 673
ROA: none217.13.63.0/24No ROA covers it. Add a ROA for AS31221, maxLength 24.673 of 673
ROA: none5.252.56.0/22No ROA covers it. Add a ROA for AS31221, maxLength 22.665 of 673
ROA: none2a02:6f0::/32No ROA covers it. Add a ROA for AS31221, maxLength 32.636 of 636

Route objects not announced

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

144.56.28.0/24RADB, RIPEValid
163.5.22.0/24RADB, RIPEValid
185.43.38.0/24RIPENo ROA
185.145.77.0/24RIPEValid
217.13.48.0/21RIPENo ROA
217.13.56.0/22RIPENo ROA

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.