Network · data from 2026-11-12

AS205952 RUSONYX-AERO LLC "ASTRA CLOUD"

Registry name: RUSONYX-AERO LLC "ASTRA CLOUD", RU · not in PeeringDB

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

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

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

24Route objects not announced registered with origin AS205952, seen from no peer

Announced routes

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


62.113.95.0/24	Valid	RIR databaseRIPE	673 100%	66
62.213.72.0/21	Valid	RIR databaseRIPE	673 100%	66
62.213.94.0/23	Valid	RIR databaseRIPE	673 100%	66
62.213.102.0/23	Valid	RIR databaseRIPE	673 100%	66
62.213.112.0/23	Valid	RIR databaseRIPE	673 100%	66
62.213.116.0/24	Valid	RIR databaseRIPE	673 100%	66
212.24.37.0/24	Valid	RIR databaseRIPE	673 100%	66
212.24.39.0/24	Valid	RIR databaseRIPE	673 100%	66
212.24.40.0/24	Valid	RIR databaseRIPE	673 100%	66
212.24.43.0/24	Valid	RIR databaseRIPE	673 100%	66
212.24.50.0/24	Valid	RIR databaseRIPE	673 100%	66
212.158.168.0/24	Valid	RIR databaseRIPE	673 100%	66
212.158.170.0/23	Valid	RIR databaseRIPE	673 100%	66
217.23.129.0/24	Valid	RIR databaseRIPE	673 100%	66
217.23.139.0/24	Valid	RIR databaseRIPE	673 100%	66
217.23.152.0/21	Valid	RIR databaseRIPE	673 100%	66
212.24.57.0/24	Valid	RIR databaseRIPE	669 99%	67
2a01:9860::/32	Valid	RIR databaseRIPE	636 100%	69

AS-SET

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

Route object: not announced24

Route objects not announced

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


62.213.72.0/24	RIPE	Invalid: maxLength
62.213.73.0/24	RIPE	Invalid: maxLength
62.213.74.0/24	RIPE	Invalid: maxLength
62.213.75.0/24	RIPE	Invalid: maxLength
62.213.76.0/24	RIPE	Invalid: maxLength
62.213.77.0/24	RIPE	Invalid: maxLength
62.213.78.0/24	RIPE	Invalid: maxLength
62.213.79.0/24	RIPE	Invalid: maxLength
62.213.80.0/24	RIPE	No ROA
62.213.81.0/24	RIPE	No ROA
62.213.94.0/24	RIPE	Invalid: maxLength
62.213.95.0/24	RIPE	Invalid: maxLength
62.213.102.0/24	RIPE	Invalid: maxLength
62.213.103.0/24	RIPE	Invalid: maxLength
62.213.112.0/24	RIPE	Invalid: maxLength
62.213.113.0/24	RIPE	Invalid: maxLength
212.158.170.0/24	RIPE	Invalid: maxLength
212.158.171.0/24	RIPE	Invalid: maxLength
212.158.174.0/23	RIPE	Valid
217.23.152.0/22	RIPE	Invalid: maxLength
217.23.156.0/22	RIPE	Invalid: maxLength
2a01:9860:1::/48	RIPE	Invalid: maxLength
2a01:9860:2::/48	RIPE	Invalid: maxLength
2a01:9860:4::/48	RIPE	Invalid: maxLength

62.213.72.0/24

RIPE

Invalid: maxLength

62.213.73.0/24

RIPE

Invalid: maxLength

62.213.74.0/24

RIPE

Invalid: maxLength

62.213.75.0/24

RIPE

Invalid: maxLength

62.213.76.0/24

RIPE

Invalid: maxLength

62.213.77.0/24

RIPE

Invalid: maxLength

62.213.78.0/24

RIPE

Invalid: maxLength

62.213.79.0/24

RIPE

Invalid: maxLength

62.213.80.0/24

RIPE

No ROA

62.213.81.0/24

RIPE

No ROA

62.213.94.0/24

RIPE

Invalid: maxLength

62.213.95.0/24

RIPE

Invalid: maxLength

62.213.102.0/24

RIPE

Invalid: maxLength

62.213.103.0/24

RIPE

Invalid: maxLength

62.213.112.0/24

RIPE

Invalid: maxLength

62.213.113.0/24

RIPE

Invalid: maxLength

212.158.170.0/24

RIPE

Invalid: maxLength

212.158.171.0/24

RIPE

Invalid: maxLength

212.158.174.0/23

RIPE

Valid

217.23.152.0/22

RIPE

Invalid: maxLength

217.23.156.0/22

RIPE

Invalid: maxLength

2a01:9860:1::/48

RIPE

Invalid: maxLength

2a01:9860:2::/48

RIPE

Invalid: maxLength

2a01:9860:4::/48

RIPE

Invalid: maxLength

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.