bgpreport

Network · data from 2026-11-12

AS21500 Scientific Production Enterprise "Technaukservice" Ltd

Registry name: TNS-AS Scientific Production Enterprise "Technaukservice" Ltd, UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21500, 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.246.220.0/22 No ROA RIR databaseRIPE 671 100% 68
193.178.248.0/22 No ROA RIR databaseRIPE 671 100% 68
195.123.177.0/24 No ROA RIR databaseRIPE 671 100% 68
195.123.184.0/24 No ROA RIR databaseRIPE 671 100% 68
195.123.185.0/24 No ROA RIR databaseRIPE 671 100% 68
194.54.186.0/24 Valid Other origin only 673 100% 66
81.17.142.0/24 Valid Other origin only 671 100% 68
62.106.68.0/24 Valid RIR databaseRIPE 671 100% 68
81.17.130.0/24 Valid RIR databaseRIPE 671 100% 68
81.17.140.0/24 Valid RIR databaseRIPE 671 100% 68
85.90.200.0/22 Valid RIR databaseRIPE 671 100% 68
92.118.224.0/24 Valid RIR databaseRIPE 671 100% 68
92.118.225.0/24 Valid RIR databaseRIPE 671 100% 68
92.118.226.0/24 Valid RIR databaseRIPE 671 100% 68
194.54.187.0/24 Valid RIR databaseRIPE 671 100% 68
195.69.184.0/22 Valid RIR databaseRIPE 671 100% 68
195.69.184.0/24 Valid RIR databaseRIPE 671 100% 68
195.69.185.0/24 Valid RIR databaseRIPE 671 100% 68
195.69.186.0/24 Valid RIR databaseRIPE 671 100% 68
195.234.220.0/22 Valid RIR databaseRIPE 671 100% 68
92.118.136.0/22 Valid RIR databaseRIPE 670 100% 68
2a06:6200::/29 Valid RIR databaseRIPE 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS21500: AS-TNSUA. 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 (AS21500 isn't in the set, or no route object for AS21500 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 objectsAS21500 in itNot covered
AS-TNSUA RIPE 444346 Yes 2

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.246.220.0/22No ROA covers it. Add a ROA for AS21500, maxLength 22.671 of 673
ROA: none193.178.248.0/22No ROA covers it. Add a ROA for AS21500, maxLength 22.671 of 673
ROA: none195.123.177.0/24No ROA covers it. Add a ROA for AS21500, maxLength 24.671 of 673
ROA: none195.123.184.0/24No ROA covers it. Add a ROA for AS21500, maxLength 24.671 of 673
ROA: none195.123.185.0/24No ROA covers it. Add a ROA for AS21500, maxLength 24.671 of 673
Route object: none194.54.186.0/24Route objects for it name AS21437, AS30790. Add a route object with origin AS21500 in the RIR database for the space.673 of 673
Route object: none81.17.142.0/24Route objects for it name AS21437, AS60455. Add a route object with origin AS21500 in the RIR database for the space.671 of 673

Route objects not announced

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

81.17.137.0/24RIPEInvalid: origin
193.111.239.0/24RIPEValid
193.178.248.0/24RIPENo ROA
195.69.187.0/24RIPEValid
195.234.220.0/23RIPEInvalid: maxLength
195.234.222.0/23RIPEInvalid: 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.