Network · data from 2026-11-12

AS201952 Atel-Rybinsk LTD AtelRybinsk

Registry name: Atel-Rybinsk LTD AtelRybinsk, RU · not in PeeringDB

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

21Route objects not announced registered with origin AS201952, seen from no peer

Announced routes

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


5.101.24.0/21	Valid	RIR databaseRIPE	673 100%	66
178.57.0.0/19	Valid	RIR databaseRIPE	673 100%	66
185.57.236.0/22	Valid	RIR databaseRIPE	673 100%	66
188.68.16.0/20	Valid	RIR databaseRIPE	673 100%	66
185.67.52.0/22	Valid	RIR databaseRIPE	670 100%	66
2a04:de80::/29	Valid	RIR databaseRIPE	635 100%	69

AS-SET

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

Route object: not announced21

Route objects not announced

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


5.101.24.0/22	RIPE	Invalid: maxLength
5.101.28.0/22	RIPE	Invalid: maxLength
178.57.0.0/20	RIPE	Invalid: maxLength
178.57.12.0/24	RIPE	Invalid: maxLength
178.57.16.0/21	RIPE	Invalid: maxLength
178.57.24.0/22	RIPE	Invalid: maxLength
178.57.28.0/22	RIPE	Invalid: maxLength
185.57.236.0/23	RIPE	Invalid: maxLength
185.57.236.0/24	RIPE	Invalid: maxLength
185.57.237.0/24	RIPE	Invalid: maxLength
185.57.238.0/23	RIPE	Invalid: maxLength
185.57.238.0/24	RIPE	Invalid: maxLength
185.57.239.0/24	RIPE	Invalid: maxLength
188.68.16.0/23	RIPE	Invalid: maxLength
188.68.16.0/24	RIPE	Invalid: maxLength
188.68.17.0/24	RIPE	Invalid: maxLength
188.68.18.0/23	RIPE	Invalid: maxLength
188.68.18.0/24	RIPE	Invalid: maxLength
188.68.19.0/24	RIPE	Invalid: maxLength
188.68.20.0/22	RIPE	Invalid: maxLength
188.68.24.0/21	RIPE	Invalid: maxLength

5.101.24.0/22

RIPE

Invalid: maxLength

5.101.28.0/22

RIPE

Invalid: maxLength

178.57.0.0/20

RIPE

Invalid: maxLength

178.57.12.0/24

RIPE

Invalid: maxLength

178.57.16.0/21

RIPE

Invalid: maxLength

178.57.24.0/22

RIPE

Invalid: maxLength

178.57.28.0/22

RIPE

Invalid: maxLength

185.57.236.0/23

RIPE

Invalid: maxLength

185.57.236.0/24

RIPE

Invalid: maxLength

185.57.237.0/24

RIPE

Invalid: maxLength

185.57.238.0/23

RIPE

Invalid: maxLength

185.57.238.0/24

RIPE

Invalid: maxLength

185.57.239.0/24

RIPE

Invalid: maxLength

188.68.16.0/23

RIPE

Invalid: maxLength

188.68.16.0/24

RIPE

Invalid: maxLength

188.68.17.0/24

RIPE

Invalid: maxLength

188.68.18.0/23

RIPE

Invalid: maxLength

188.68.18.0/24

RIPE

Invalid: maxLength

188.68.19.0/24

RIPE

Invalid: maxLength

188.68.20.0/22

RIPE

Invalid: maxLength

188.68.24.0/21

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.