Network · data from 2026-11-12

AS202636 echelon Invermae Solutions SL

Registry name: echelon Invermae Solutions SL, ES · not in PeeringDB

26IPv4 routes 92.3% RPKI valid · 96.2% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

2No ROA 1 with no route object for this origin

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

3Route objects not announced registered with origin AS202636, seen from no peer

Announced routes

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


185.49.226.0/23	No ROA	RIR databaseRIPE	673 100%	67
194.124.214.0/23	No ROA	RIR databaseRIPE	673 100%	67
185.199.55.0/24	Valid	Other origin only	673 100%	67
37.32.96.0/23	Valid	RIR databaseRIPE	673 100%	67
91.246.52.0/24	Valid	RIR databaseRIPE	673 100%	67
93.92.228.0/22	Valid	RIR databaseRIPE	673 100%	67
93.189.121.0/24	Valid	RIR databaseRIPE	673 100%	67
93.189.122.0/24	Valid	RIR databaseRIPE	673 100%	67
95.214.144.0/22	Valid	RIR databaseRIPE	673 100%	67
185.142.200.0/24	Valid	RIR databaseRIPE	673 100%	67
185.142.201.0/24	Valid	RIR databaseRIPE	673 100%	67
185.142.202.0/24	Valid	RIR databaseRIPE	673 100%	67
185.142.203.0/24	Valid	RIR databaseRIPE	673 100%	67
185.150.77.0/24	Valid	RIR databaseRIPE	673 100%	67
185.150.78.0/23	Valid	RIR databaseRIPE	673 100%	67
185.179.233.0/24	Valid	RIR databaseRIPE	673 100%	67
185.179.235.0/24	Valid	RIR databaseRIPE	673 100%	67
185.191.44.0/22	Valid	RIR databaseRIPE	673 100%	67
185.218.18.0/24	Valid	RIR databaseRIPE	673 100%	67
185.227.205.0/24	Valid	RIR databaseRIPE	673 100%	67
185.239.254.0/24	Valid	RIR databaseRIPE	673 100%	67
185.248.200.0/22	Valid	RIR databaseRIPE	673 100%	67
185.252.44.0/22	Valid	RIR databaseRIPE	673 100%	67
212.80.208.0/22	Valid	RIR databaseRIPE	673 100%	67
217.67.160.0/24	Valid	RIR databaseRIPE	673 100%	67
45.90.238.0/24	Valid	RIR databaseRIPE	672 100%	67

AS-SET

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

ROA: none2
Route object: none1
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.49.226.0/23	No ROA covers it. Add a ROA for AS202636, maxLength 23.	673 of 673
ROA: none	194.124.214.0/23	No ROA covers it. Add a ROA for AS202636, maxLength 23.	673 of 673
Route object: none	185.199.55.0/24	Route objects for it name AS201942. Add a route object with origin AS202636 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.49.226.0/23

No ROA covers it. Add a ROA for AS202636, maxLength 23.

673 of 673

ROA: none

194.124.214.0/23

No ROA covers it. Add a ROA for AS202636, maxLength 23.

673 of 673

Route object: none

185.199.55.0/24

Route objects for it name AS201942. Add a route object with origin AS202636 in the RIR database for the space.

673 of 673

Route objects not announced

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


158.255.232.0/23	RIPE	No ROA
185.49.224.0/23	RIPE	No ROA
185.76.76.0/24	RIPE	No ROA

158.255.232.0/23

RIPE

No ROA

185.49.224.0/23

RIPE

No ROA

185.76.76.0/24

RIPE

No 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.