bgpreport

Network · data from 2026-11-12

AS50473 Altagen

Registry name: ECO-AS Altagen JSC, RU · PeeringDB

26IPv4 routes 50.0% RPKI valid · 69.2% with a route object
0IPv6 routes
4RPKI invalid 0 origin · 4 maxLength
9No ROA 8 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS50473, seen from no peer

Announced routes

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

188.64.166.0/24 Invalid: maxLength Nonecovered by 188.64.166.0/23 19 3%low visibility 14
188.64.167.0/24 Invalid: maxLength Nonecovered by 188.64.166.0/23 19 3%low visibility 14
46.151.159.246/32 Invalid: maxLength Nonecovered by 46.151.152.0/21 3 0%low visibility 6
185.21.159.0/24 Invalid: maxLength RIR databaseRIPE 56 8%low visibility 30
194.36.199.0/24 No ROA Nonecovered by 194.36.196.0/22 673 100% 66
194.36.197.0/24 No ROA Nonecovered by 194.36.196.0/22 672 100% 66
94.141.244.0/22 No ROA RIR databaseRIPE 672 100% 66
94.141.252.0/22 No ROA RIR databaseRIPE 672 100% 66
83.137.48.0/21 No ROA RIR databaseRIPE 671 100% 68
185.26.28.0/22 No ROA RIR databaseRIPE 671 100% 68
185.42.124.0/22 No ROA RIR databaseRIPE 671 100% 68
185.191.56.0/22 No ROA RIR databaseRIPE 671 100% 68
194.36.196.0/22 No ROA RIR databaseRIPE 671 100% 68
185.42.124.0/23 Valid Nonecovered by 185.42.124.0/22 673 100% 66
185.42.126.0/23 Valid Nonecovered by 185.42.124.0/22 673 100% 66
46.151.155.0/24 Valid Nonecovered by 46.151.152.0/21 80 12% 31
193.105.59.0/24 Valid RIR databaseRIPE 673 100% 66
46.151.152.0/21 Valid RIR databaseRIPE 671 100% 68
80.251.224.0/20 Valid RIR databaseRIPE 671 100% 68
91.214.240.0/22 Valid RIR databaseRIPE 671 100% 68
177.29.249.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
185.21.156.0/22 Valid RIR databaseRIPE 671 100% 68
185.61.76.0/22 Valid RIR databaseRIPE 671 100% 68
188.64.165.0/24 Valid RIR databaseRIPE 671 100% 68
188.64.166.0/23 Valid RIR databaseRIPE 671 100% 68
195.216.241.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

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

NameDatabaseASNsSets Route objectsAS50473 in itNot covered
AS-ECO RIPE1 member set in no database: AS-INFOSET 8247 Yes 1

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

  • ROA: maxLength4
  • ROA: none9
  • Route object: none8
  • AS-SET: missing member1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: maxLength188.64.166.0/24ROA 188.64.166.0/23 AS50473 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 188.64.166.0/24.19 of 673
Route object: none188.64.166.0/24No route object for it. A route object for 188.64.166.0/23 with origin AS50473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50473 in the RIR database for the space.19 of 673
ROA: maxLength188.64.167.0/24ROA 188.64.166.0/23 AS50473 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 188.64.167.0/24.19 of 673
Route object: none188.64.167.0/24No route object for it. A route object for 188.64.166.0/23 with origin AS50473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50473 in the RIR database for the space.19 of 673
ROA: maxLength46.151.159.246/32ROA 46.151.152.0/21 AS50473 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 46.151.159.246/32.3 of 673
Route object: none46.151.159.246/32No route object for it. A route object for 46.151.152.0/21 with origin AS50473 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS50473 in the RIR database for the space.3 of 673
ROA: maxLength185.21.159.0/24ROA 185.21.156.0/22 AS50473 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.21.159.0/24.56 of 673
ROA: none194.36.199.0/24No ROA covers it. Add a ROA for AS50473, maxLength 24.673 of 673
Route object: none194.36.199.0/24No route object for it. A route object for 194.36.196.0/22 with origin AS50473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50473 in the RIR database for the space.673 of 673
ROA: none194.36.197.0/24No ROA covers it. Add a ROA for AS50473, maxLength 24.672 of 673
Route object: none194.36.197.0/24No route object for it. A route object for 194.36.196.0/22 with origin AS50473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50473 in the RIR database for the space.672 of 673
ROA: none94.141.244.0/22No ROA covers it. Add a ROA for AS50473, maxLength 22.672 of 673
ROA: none94.141.252.0/22No ROA covers it. Add a ROA for AS50473, maxLength 22.672 of 673
ROA: none83.137.48.0/21No ROA covers it. Add a ROA for AS50473, maxLength 21.671 of 673
ROA: none185.26.28.0/22No ROA covers it. Add a ROA for AS50473, maxLength 22.671 of 673
ROA: none185.42.124.0/22No ROA covers it. Add a ROA for AS50473, maxLength 22.671 of 673
ROA: none185.191.56.0/22No ROA covers it. Add a ROA for AS50473, maxLength 22.671 of 673
ROA: none194.36.196.0/22No ROA covers it. Add a ROA for AS50473, maxLength 22.671 of 673
Route object: none185.42.124.0/23No route object for it. A route object for 185.42.124.0/22 with origin AS50473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50473 in the RIR database for the space.673 of 673
Route object: none185.42.126.0/23No route object for it. A route object for 185.42.124.0/22 with origin AS50473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50473 in the RIR database for the space.673 of 673
Route object: none46.151.155.0/24No route object for it. A route object for 46.151.152.0/21 with origin AS50473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50473 in the RIR database for the space.80 of 673
AS-SET: missing memberAS-ECOAS-ECO (RIPE) lists AS-INFOSET; no IRR database read has it.

Route objects not announced

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

154.196.162.0/24AFRINIC, RADBValid
154.196.177.0/24AFRINIC, RADBValid
154.196.254.0/24AFRINIC, RADBValid
168.113.144.0/23RIPENo ROA
168.113.146.0/23RIPENo ROA
168.113.148.0/23RIPENo ROA
168.113.150.0/23RIPENo ROA
185.21.156.0/24RIPEInvalid: maxLength
185.21.157.0/24RIPEInvalid: maxLength
185.21.158.0/24RIPEInvalid: 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.