bgpreport

Network · data from 2026-11-12

AS28769 STTK-AS Joint Stock Company TransTeleCom

Registry name: STTK-AS Joint Stock Company TransTeleCom, RU · not in PeeringDB

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

Announced routes

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

80.240.38.0/24 No ROA RIR databaseRIPE 670 100% 66
46.166.98.0/24 Valid Nonecovered by 46.166.96.0/22 671 100% 66
46.166.99.0/24 Valid Nonecovered by 46.166.96.0/22 671 100% 66
46.166.104.0/22 Valid Nonecovered by 46.166.96.0/20 671 100% 66
46.166.114.0/24 Valid Nonecovered by 46.166.96.0/19 671 100% 66
93.188.208.0/23 Valid Nonecovered by 93.188.208.0/21 671 100% 66
31.216.161.0/24 Valid RIR databaseRIPE 671 100% 66
31.216.166.0/24 Valid RIR databaseRIPE 671 100% 66
31.216.167.0/24 Valid RIR databaseRIPE 671 100% 66
46.166.66.0/24 Valid RIR databaseRIPE 671 100% 66
46.166.67.0/24 Valid RIR databaseRIPE 671 100% 66
46.166.92.0/24 Valid RIR databaseRIPE 671 100% 66
46.182.132.0/22 Valid RIR databaseRIPE 671 100% 66
80.240.36.0/23 Valid RIR databaseRIPE 671 100% 66
93.188.210.0/24 Valid RIR databaseRIPE 671 100% 66
80.240.32.0/24 Valid RIR databaseRIPE 670 100% 66
80.240.33.0/24 Valid RIR databaseRIPE 670 100% 66
80.240.34.0/24 Valid RIR databaseRIPE 670 100% 66
80.240.35.0/24 Valid RIR databaseRIPE 670 100% 66
80.240.47.0/24 Valid RIR databaseRIPE 670 100% 66
2a06:e0c0::/32 Valid RIR databaseRIPE 635 100% 67
2a06:e0c1::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none5
  • Route object: not announced67
ChangePrefix or setDetailFull-table peers
ROA: none80.240.38.0/24No ROA covers it. Add a ROA for AS28769, maxLength 24.670 of 673
Route object: none46.166.98.0/24No route object for it. A route object for 46.166.96.0/22 with origin AS28769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28769 in the RIR database for the space.671 of 673
Route object: none46.166.99.0/24No route object for it. A route object for 46.166.96.0/22 with origin AS28769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28769 in the RIR database for the space.671 of 673
Route object: none46.166.104.0/22No route object for it. A route object for 46.166.96.0/20 with origin AS28769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28769 in the RIR database for the space.671 of 673
Route object: none46.166.114.0/24No route object for it. A route object for 46.166.96.0/19 with origin AS28769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28769 in the RIR database for the space.671 of 673
Route object: none93.188.208.0/23No route object for it. A route object for 93.188.208.0/21 with origin AS28769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28769 in the RIR database for the space.671 of 673

Route objects not announced

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

31.216.160.0/20RIPENo ROA
31.216.160.0/23RIPEValid
31.216.160.0/24RIPEValid
31.216.162.0/24RIPEValid
31.216.163.0/24RIPEValid
31.216.164.0/24RIPEInvalid: maxLength
31.216.165.0/24RIPEInvalid: maxLength
31.216.168.0/24RIPEInvalid: maxLength
31.216.169.0/24RIPEInvalid: maxLength
31.216.171.0/24RIPEValid
31.216.172.0/24RIPEInvalid: maxLength
31.216.173.0/24RIPEInvalid: maxLength
31.216.174.0/24RIPEInvalid: maxLength
31.216.175.0/24RIPEInvalid: maxLength
46.166.64.0/18RIPENo ROA
46.166.64.0/24RIPENo ROA
46.166.65.0/24RIPEValid
46.166.68.0/24RIPENo ROA
46.166.69.0/24RIPENo ROA
46.166.70.0/24RIPENo ROA
46.166.71.0/24RIPENo ROA
46.166.72.0/22RIPENo ROA
46.166.76.0/23RIPENo ROA
46.166.78.0/24RIPEValid
46.166.79.0/24RIPEValid
46.166.80.0/20RIPENo ROA
46.166.96.0/19RIPENo ROA
46.166.96.0/20RIPENo ROA
46.166.96.0/22RIPENo ROA
46.166.100.0/23RIPENo ROA
46.182.128.0/21RIPENo ROA
46.182.128.0/22RIPEValid
46.182.128.0/23RIPEInvalid: maxLength
46.182.128.0/24RIPEInvalid: maxLength
46.182.129.0/24RIPEInvalid: maxLength
46.182.130.0/24RIPEInvalid: maxLength
46.182.131.0/24RIPEValid
46.182.132.0/24RIPEInvalid: maxLength
46.182.133.0/24RIPEInvalid: maxLength
46.182.134.0/24RIPEInvalid: maxLength
46.182.135.0/24RIPEInvalid: maxLength
80.240.32.0/20RIPENo ROA
80.240.32.0/23RIPENo ROA
80.240.36.0/24RIPEInvalid: maxLength
80.240.37.0/24RIPEInvalid: maxLength
80.240.39.0/24RIPENo ROA
80.240.40.0/21RIPENo ROA
80.240.40.0/22RIPENo ROA
80.240.40.0/24RIPENo ROA
80.240.41.0/24RIPENo ROA
80.240.42.0/24RIPENo ROA
80.240.43.0/24RIPENo ROA
80.240.44.0/24RIPEValid
80.240.45.0/24RIPENo ROA
80.240.46.0/24RIPENo ROA
93.188.208.0/21RIPENo ROA
93.188.208.0/24RIPEInvalid: maxLength
93.188.209.0/24RIPEInvalid: maxLength
93.188.211.0/24RIPENo ROA
93.188.212.0/24RIPENo ROA
93.188.213.0/24RIPENo ROA
93.188.214.0/24RIPENo ROA
93.188.215.0/24RIPEValid
185.131.172.0/22RIPENo ROA
185.131.174.0/23RIPENo ROA
2a06:e0c2::/32RIPEValid
2a06:e0c3::/32RIPEValid

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.