Network · data from 2026-11-12

AS214891 CLOUDRIX RU

Registry name: CLOUDRIX-RU Denis Aleksandrovich Iakovlev, RU · PeeringDB

7IPv4 routes 100.0% RPKI valid · 85.7% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


31.76.34.0/24	Valid	None	668 99%	66
2a10:ab80::/29	Valid	None	632 99%	67
31.58.238.0/24	Valid	RIR databaseRIPE	670 100%	68
31.58.239.0/24	Valid	RIR databaseRIPE	670 100%	68
95.85.240.0/24	Valid	RIR databaseRIPE	670 100%	68
138.124.254.0/24	Valid	RIR databaseRIPE	670 100%	68
138.124.255.0/24	Valid	RIR databaseRIPE	670 100%	68
144.31.190.0/24	Valid	RIR databaseRIPE	670 100%	68
2a0d:d940:c0::/44	Valid	RIR databaseRIPE	635 100%	69
2a12:bec4:1280::/44	Valid	RIR databaseRIPE	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS214891: AS214891:AS-CLOUDRIX. 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 (AS214891 isn't in the set, or no route object for AS214891 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.

Name	Database	ASNs	Sets	Route objects	AS214891 in it	Not covered
AS214891:AS-CLOUDRIX	RIPE	12	5	334	Yes	2

Name

Database

ASNs

Sets

Route objects

AS214891 in it

Not covered

AS214891:AS-CLOUDRIX

RIPE

334

Yes

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

Route object: none2

Change	Prefix or set	Detail	Full-table peers
Route object: none	31.76.34.0/24	No route object for it. Add a route object with origin AS214891 in the RIR database for the space.	668 of 673
Route object: none	2a10:ab80::/29	No route object for it. Add a route object with origin AS214891 in the RIR database for the space.	632 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

31.76.34.0/24

No route object for it. Add a route object with origin AS214891 in the RIR database for the space.

668 of 673

Route object: none

2a10:ab80::/29

No route object for it. Add a route object with origin AS214891 in the RIR database for the space.

632 of 636

Route objects not announced

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