Network · data from 2026-11-12

AS50098 AS-CLOUVO Melbikomas UAB

Registry name: AS-CLOUVO Melbikomas UAB, LT · not in PeeringDB

23IPv4 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

10Route objects not announced registered with origin AS50098, seen from no peer

Announced routes

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


88.218.240.0/22	Valid	RIR databaseRIPE	673 100%	67
91.192.80.0/24	Valid	RIR databaseRIPE	673 100%	67
93.189.58.0/24	Valid	RIR databaseRIPE	673 100%	67
93.189.63.0/24	Valid	RIR databaseRIPE	673 100%	67
95.81.70.0/24	Valid	RIR databaseRIPE	673 100%	67
95.81.71.0/24	Valid	RIR databaseRIPE	673 100%	67
95.81.106.0/24	Valid	RIR databaseRIPE	673 100%	67
95.81.111.0/24	Valid	RIR databaseRIPE	673 100%	67
185.131.64.0/24	Valid	RIR databaseRIPE	673 100%	67
185.131.67.0/24	Valid	RIR databaseRIPE	673 100%	67
185.246.154.0/24	Valid	RIR databaseRIPE	673 100%	67
195.211.220.0/24	Valid	RIR databaseRIPE	673 100%	67
195.211.221.0/24	Valid	RIR databaseRIPE	673 100%	66
213.111.132.0/23	Valid	RIR databaseRIPE	673 100%	67
213.183.32.0/24	Valid	RIR databaseRIPE	673 100%	67
213.183.33.0/24	Valid	RIR databaseRIPE	673 100%	67
213.183.41.0/24	Valid	RIR databaseRIPE	673 100%	67
213.183.45.0/24	Valid	RIR databaseRIPE	673 100%	67
213.183.48.0/24	Valid	RIR databaseRIPE	673 100%	67
213.183.53.0/24	Valid	RIR databaseRIPE	673 100%	67
213.183.58.0/24	Valid	RIR databaseRIPE	673 100%	67
195.211.222.0/24	Valid	RIR databaseRIPE	667 99%	67
195.211.223.0/24	Valid	RIR databaseRIPE	667 99%	67

AS-SET

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

Route object: not announced10

Route objects not announced

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


88.218.240.0/24	RIPE	Valid
88.218.241.0/24	RIPE	Valid
88.218.242.0/24	RIPE	Valid
88.218.243.0/24	RIPE	Valid
195.211.220.0/22	RIPE	No ROA
195.211.221.0/30	RIPE	Invalid: maxLength
195.211.221.1/32	RIPE	Invalid: maxLength
195.211.223.27/32	RIPE	Invalid: maxLength
213.111.132.0/24	RIPE	Valid
213.111.133.0/24	RIPE	Valid

88.218.240.0/24

RIPE

Valid

88.218.241.0/24

RIPE

Valid

88.218.242.0/24

RIPE

Valid

88.218.243.0/24

RIPE

Valid

195.211.220.0/22

RIPE

No ROA

195.211.221.0/30

RIPE

Invalid: maxLength

195.211.221.1/32

RIPE

Invalid: maxLength

195.211.223.27/32

RIPE

Invalid: maxLength

213.111.132.0/24

RIPE

Valid

213.111.133.0/24

RIPE

Valid

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.