bgpreport

Network · data from 2026-11-12

AS44266 TEHNO-AS TEHNO Limited Company

Registry name: TEHNO-AS TEHNO Limited Company, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44266, 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.204.144.0/22 No ROA RIR databaseRIPE 425 63% 65
195.93.164.0/23 No ROA RIR databaseRIPE 425 63% 65
185.5.16.0/22 No ROA RIR databaseRIPE 416 62% 64
77.243.0.0/20 No ROA RIR databaseRIPE 414 62% 64
128.65.136.0/21 No ROA RIR databaseRIPE 414 62% 64
195.49.184.0/22 No ROA RIR databaseRIPE 414 62% 64

AS-SET

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

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none91.204.144.0/22No ROA covers it. Add a ROA for AS44266, maxLength 22.425 of 673
ROA: none195.93.164.0/23No ROA covers it. Add a ROA for AS44266, maxLength 23.425 of 673
ROA: none185.5.16.0/22No ROA covers it. Add a ROA for AS44266, maxLength 22.416 of 673
ROA: none77.243.0.0/20No ROA covers it. Add a ROA for AS44266, maxLength 20.414 of 673
ROA: none128.65.136.0/21No ROA covers it. Add a ROA for AS44266, maxLength 21.414 of 673
ROA: none195.49.184.0/22No ROA covers it. Add a ROA for AS44266, maxLength 22.414 of 673

Route objects not announced

Every route object with origin AS44266 is announced.

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.