bgpreport

Network · data from 2026-11-12

AS34479 tsc-as "Computational technologies - consulting" LLC

Registry name: tsc-as "Computational technologies - consulting" LLC, RU · not in PeeringDB

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

Announced routes

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

84.237.4.0/23 No ROA Nonecovered by 84.237.0.0/20 672 100% 67
84.237.6.0/23 No ROA RIR databaseRIPE 673 100% 66
84.237.11.0/24 No ROA RIR databaseRIPE 673 100% 66
84.237.0.0/22 No ROA RIR databaseRIPE 672 100% 66
217.79.56.0/23 No ROA RIR databaseRIPE 672 100% 66

AS-SET

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

  • ROA: none5
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none84.237.4.0/23No ROA covers it. Add a ROA for AS34479, maxLength 23.672 of 673
Route object: none84.237.4.0/23No route object for it. A route object for 84.237.0.0/20 with origin AS34479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34479 in the RIR database for the space.672 of 673
ROA: none84.237.6.0/23No ROA covers it. Add a ROA for AS34479, maxLength 23.673 of 673
ROA: none84.237.11.0/24No ROA covers it. Add a ROA for AS34479, maxLength 24.673 of 673
ROA: none84.237.0.0/22No ROA covers it. Add a ROA for AS34479, maxLength 22.672 of 673
ROA: none217.79.56.0/23No ROA covers it. Add a ROA for AS34479, maxLength 23.672 of 673

Route objects not announced

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

84.237.0.0/20RIPENo ROA
84.237.8.0/23RIPENo ROA
84.237.10.0/24RIPENo ROA
84.237.12.0/23RIPENo 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.