bgpreport

Network · data from 2026-11-12

AS50628 Leonix Telecom

Registry name: Leonix-Telecom Leonix Telecom SAS, FR · PeeringDB

12IPv4 routes 83.3% RPKI valid · 83.3% with a route object
7IPv6 routes 71.4% RPKI valid · 71.4% with a route object
1RPKI invalid 0 origin · 1 maxLength
3No ROA 4 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS50628, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50628, 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.
2a0b:3b02:2006::/48 Invalid: maxLength Nonecovered by 2a0b:3b00::/29 1 0%low visibility 1
0.0.0.0/0 bogon No ROA None 0 0%low visibility 1
::/0 bogon No ROA None 0 0%low visibility 1
95.214.196.0/22 No ROA RIR databaseRIPE 672 100% 66
45.144.94.0/23 Valid None 672 100% 66
178.208.0.0/19 Valid RIR databaseRIPE 672 100% 66
185.173.68.0/22 Valid RIR databaseRIPE 672 100% 66
185.173.96.0/22 Valid RIR databaseRIPE 672 100% 66
185.194.156.0/22 Valid RIR databaseRIPE 672 100% 66
193.35.98.0/24 Valid RIR databaseRIPE 672 100% 66
193.35.101.0/24 Valid RIR databaseRIPE 672 100% 66
193.35.145.0/24 Valid RIR databaseRIPE 672 100% 66
193.35.156.0/24 Valid RIR databaseRIPE 672 100% 66
193.202.0.0/24 Valid RIR databaseRIPE 672 100% 66
2a04:3d80::/29 Valid RIR databaseRIPE 634 100% 67
2a0b:3b00::/29 Valid RIR databaseRIPE 634 100% 67
2a0b:4700::/29 Valid RIR databaseRIPE 634 100% 67
2a0e:d500::/29 Valid RIR databaseRIPE 634 100% 67
2a0e:ebc0::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS50628: RIPE::AS-LEONIX. 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 (AS50628 isn't in the set, or no route object for AS50628 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 objectsAS50628 in itNot covered
RIPE::AS-LEONIX RIPElists itself further down 3117118 Yes 3

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: maxLength1
  • Bogon prefix2
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a0b:3b02:2006::/48ROA 2a0b:3b00::/29 AS50628 has maxLength 29; the route is a /48. Raise the maxLength, or add a ROA for 2a0b:3b02:2006::/48.1 of 636
Route object: none2a0b:3b02:2006::/48No route object for it. A route object for 2a0b:3b00::/29 with origin AS50628 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50628 in the RIR database for the space.1 of 636
Bogon prefix0.0.0.0/0In IANA's special-purpose registry: default route.0 of 673
Bogon prefix::/0In IANA's special-purpose registry: default route.0 of 636
ROA: none95.214.196.0/22No ROA covers it. Add a ROA for AS50628, maxLength 22.672 of 673
Route object: none45.144.94.0/23No route object for it. Add a route object with origin AS50628 in the RIR database for the space.672 of 673

Route objects not announced

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