Network · data from 2026-11-12

AS43967 TEREMKI-AS TEREMKY LAN ISP LLC

Registry name: TEREMKI-AS TEREMKY LAN ISP LLC, UA · not in PeeringDB

45IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

10Route objects not announced registered with origin AS43967, seen from no peer

Announced routes

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


193.160.97.0/24	Valid	RIR databaseRIPE	673 100%	66
195.158.196.0/24	Valid	RIR databaseRIPE	673 100%	66
195.158.197.0/24	Valid	RIR databaseRIPE	673 100%	66
45.159.100.0/24	Valid	RIR databaseRIPE	672 100%	66
45.159.101.0/24	Valid	RIR databaseRIPE	672 100%	66
45.159.102.0/24	Valid	RIR databaseRIPE	672 100%	66
195.158.198.0/24	Valid	RIR databaseRIPE	672 100%	66
195.158.199.0/24	Valid	RIR databaseRIPE	672 100%	66
91.200.180.0/24	Valid	RIR databaseRIPE	671 100%	68
91.200.181.0/24	Valid	RIR databaseRIPE	671 100%	68
91.200.182.0/24	Valid	RIR databaseRIPE	671 100%	68
91.200.183.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.224.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.225.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.226.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.227.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.228.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.229.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.230.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.231.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.232.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.233.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.234.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.235.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.236.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.237.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.238.0/24	Valid	RIR databaseRIPE	671 100%	68
178.159.239.0/24	Valid	RIR databaseRIPE	671 100%	68
194.31.44.0/22	Valid	RIR databaseRIPE	671 100%	68
194.31.44.0/24	Valid	RIR databaseRIPE	671 100%	68
194.31.45.0/24	Valid	RIR databaseRIPE	671 100%	68
194.31.46.0/24	Valid	RIR databaseRIPE	671 100%	68
194.31.47.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.136.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.137.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.138.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.139.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.140.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.141.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.142.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.143.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.144.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.145.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.146.0/24	Valid	RIR databaseRIPE	671 100%	68
195.211.147.0/24	Valid	RIR databaseRIPE	671 100%	68

AS-SET

AS43967 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.

Route object: not announced10

Route objects not announced

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


45.159.103.0/24	RIPE	Valid
91.200.180.0/22	RIPE	No ROA
178.159.224.0/22	RIPE	No ROA
178.159.228.0/22	RIPE	No ROA
178.159.232.0/22	RIPE	No ROA
178.159.236.0/22	RIPE	No ROA
195.158.196.0/22	RIPE	Valid
195.211.136.0/22	RIPE	No ROA
195.211.140.0/22	RIPE	No ROA
195.211.144.0/22	RIPE	No ROA

45.159.103.0/24

RIPE

Valid

91.200.180.0/22

RIPE

No ROA

178.159.224.0/22

RIPE

No ROA

178.159.228.0/22

RIPE

No ROA

178.159.232.0/22

RIPE

No ROA

178.159.236.0/22

RIPE

No ROA

195.158.196.0/22

RIPE

Valid

195.211.136.0/22

RIPE

No ROA

195.211.140.0/22

RIPE

No ROA

195.211.144.0/22

RIPE

No 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.