bgpreport

Network · data from 2026-11-12

AS34629 ORNRU-AS "Resurs-Svyaz" Ltd

Registry name: ORNRU-AS "Resurs-Svyaz" Ltd, RU · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 62.5% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 3 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS34629, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS34629, 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.225.177.0/24 No ROA Nonecovered by 185.225.176.0/22 2 0%low visibility 2
185.225.178.0/24 No ROA Nonecovered by 185.225.176.0/22 2 0%low visibility 2
185.225.179.0/24 No ROA Nonecovered by 185.225.176.0/22 2 0%low visibility 2
80.76.176.0/20 No ROA RIR databaseRIPE 673 100% 66
188.116.128.0/18 No ROA RIR databaseRIPE 673 100% 66
195.66.126.0/24 No ROA RIR databaseRIPE 673 100% 66
217.174.0.0/20 No ROA RIR databaseRIPE 673 100% 66
194.169.250.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
2a07:dc40::/32 No ROA RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: none9
  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none185.225.177.0/24No ROA covers it. Add a ROA for AS34629, maxLength 24.2 of 673
Route object: none185.225.177.0/24No route object for it. A route object for 185.225.176.0/22 with origin AS34629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34629 in the RIR database for the space.2 of 673
ROA: none185.225.178.0/24No ROA covers it. Add a ROA for AS34629, maxLength 24.2 of 673
Route object: none185.225.178.0/24No route object for it. A route object for 185.225.176.0/22 with origin AS34629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34629 in the RIR database for the space.2 of 673
ROA: none185.225.179.0/24No ROA covers it. Add a ROA for AS34629, maxLength 24.2 of 673
Route object: none185.225.179.0/24No route object for it. A route object for 185.225.176.0/22 with origin AS34629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34629 in the RIR database for the space.2 of 673
ROA: none80.76.176.0/20No ROA covers it. Add a ROA for AS34629, maxLength 20.673 of 673
ROA: none188.116.128.0/18No ROA covers it. Add a ROA for AS34629, maxLength 18.673 of 673
ROA: none195.66.126.0/24No ROA covers it. Add a ROA for AS34629, maxLength 24.673 of 673
ROA: none217.174.0.0/20No ROA covers it. Add a ROA for AS34629, maxLength 20.673 of 673
ROA: none194.169.250.0/24No ROA covers it. Add a ROA for AS34629, maxLength 24.2 of 673
ROA: none2a07:dc40::/32No ROA covers it. Add a ROA for AS34629, maxLength 32.2 of 636

Route objects not announced

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

80.76.176.0/21RIPENo ROA
80.76.184.0/21RIPENo ROA
185.225.176.0/22RIPENo 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.