Network · data from 2026-11-12

AS9180 ALIENOR Alienor.net SARL

Registry name: ALIENOR Alienor.net SARL, FR · not in PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

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

Announced routes

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


194.3.190.0/24	Valid	RIR databaseRIPE	672 100%	66
194.206.120.0/24	Valid	RIR databaseRIPE	672 100%	66
194.250.118.0/24	Valid	RIR databaseRIPE	672 100%	66
195.101.64.0/24	Valid	RIR databaseRIPE	672 100%	66
195.101.188.0/24	Valid	RIR databaseRIPE	672 100%	66
195.101.189.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.224.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.225.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.226.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.227.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.228.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.229.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.230.0/24	Valid	RIR databaseRIPE	672 100%	66
195.214.231.0/24	Valid	RIR databaseRIPE	672 100%	66
217.109.127.0/24	Valid	RIR databaseRIPE	672 100%	66

AS-SET

AS9180 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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