Network · data from 2026-11-12

AS214587 Rulx Alexis

Registry name: Rulx-Philome-Alexis Rulx Alexis, LU · PeeringDB

0IPv4 routes

3IPv6 routes 66.7% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

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

Announced routes

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


2a13:7fc0:1015::/48	No ROA	RIR databaseRIPE	1 0%low visibility	2
2a13:7fc0:1010::/48	Valid	RIR databaseRADB, RIPE	607 95%	68
2a13:7fc0:101f::/48	Valid	RIR databaseRIPE	607 95%	68

2a13:7fc0:1015::/48

No ROA

RIR databaseRIPE

1 0%low visibility

2a13:7fc0:1010::/48

Valid

RIR databaseRADB, RIPE

607 95%

2a13:7fc0:101f::/48

Valid

RIR databaseRIPE

607 95%

AS-SET

AS214587's PeeringDB record names no 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 1 are in fix.csv.

ROA: none1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2a13:7fc0:1015::/48	No ROA covers it. Add a ROA for AS214587, maxLength 48.	1 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2a13:7fc0:1015::/48

No ROA covers it. Add a ROA for AS214587, maxLength 48.

1 of 636

Route objects not announced

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