bgpreport

Network · data from 2026-11-12

AS50916 Nadym Svyaz Service

Registry name: NADYMSS-AS Yan Telecom Ltd, RU · PeeringDB

6IPv4 routes 16.7% RPKI valid · 66.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS50916, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50916, 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.
91.221.48.0/23 No ROA None 673 100% 66
195.242.216.0/23 No ROA None 2 0%low visibility 2
91.238.222.0/23 No ROA RIR databaseRIPE 673 100% 66
195.191.220.0/23 No ROA RIR databaseRIPE 673 100% 66
195.242.216.0/24 No ROA RIR databaseRIPE 673 100% 66
93.170.124.0/22 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS50916's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none91.221.48.0/23No ROA covers it. Add a ROA for AS50916, maxLength 23.673 of 673
Route object: none91.221.48.0/23No route object for it. Add a route object with origin AS50916 in the RIR database for the space.673 of 673
ROA: none195.242.216.0/23No ROA covers it. Add a ROA for AS50916, maxLength 23.2 of 673
Route object: none195.242.216.0/23No route object for it. Add a route object with origin AS50916 in the RIR database for the space.2 of 673
ROA: none91.238.222.0/23No ROA covers it. Add a ROA for AS50916, maxLength 23.673 of 673
ROA: none195.191.220.0/23No ROA covers it. Add a ROA for AS50916, maxLength 23.673 of 673
ROA: none195.242.216.0/24No ROA covers it. Add a ROA for AS50916, maxLength 24.673 of 673

Route objects not announced

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

91.221.48.0/24RIPENo ROA
91.221.49.0/24RIPENo ROA
91.238.222.0/24RIPENo ROA
91.238.223.0/24RIPENo ROA
195.191.220.0/24RIPENo ROA
195.191.221.0/24RIPENo 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.