Network · data from 2026-11-12

AS52026 TRUF-AS TRUF d.o.o.

Registry name: TRUF-AS TRUF d.o.o., RS · not in PeeringDB

50IPv4 routes 100.0% RPKI valid · 98.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

5Route objects not announced registered with origin AS52026, seen from no peer

Announced routes

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


109.206.99.0/24	Valid	Other origin onlycovered by 109.206.96.0/19	672 100%	66
91.234.132.0/22	Valid	RIR databaseRIPE	673 100%	66
91.234.132.0/23	Valid	RIR databaseRIPE	673 100%	66
91.234.134.0/23	Valid	RIR databaseRIPE	673 100%	66
109.206.96.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.97.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.98.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.100.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.101.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.102.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.103.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.104.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.105.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.106.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.107.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.108.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.109.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.110.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.111.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.112.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.113.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.114.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.115.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.116.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.117.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.118.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.119.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.120.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.121.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.122.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.123.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.124.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.125.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.126.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.127.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.32.0/22	Valid	RIR databaseRIPE	672 100%	66
109.207.33.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.34.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.35.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.36.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.37.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.38.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.39.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.40.0/22	Valid	RIR databaseRIPE	672 100%	66
109.207.44.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.45.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.46.0/24	Valid	RIR databaseRIPE	672 100%	66
109.207.47.0/24	Valid	RIR databaseRIPE	672 100%	66
109.206.96.0/19	Valid	RIR databaseRIPE	671 100%	66
109.207.32.0/20	Valid	RIR databaseRIPE	671 100%	66

AS-SET

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

Route object: none1
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: none	109.206.99.0/24	Route objects for it name AS198421. A route object for 109.206.96.0/19 with origin AS52026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52026 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

109.206.99.0/24

Route objects for it name AS198421. A route object for 109.206.96.0/19 with origin AS52026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52026 in the RIR database for the space.

672 of 673

Route objects not announced

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


109.207.32.0/24	RIPE	Valid
109.207.40.0/24	RIPE	Valid
109.207.41.0/24	RIPE	Valid
109.207.42.0/24	RIPE	Valid
109.207.43.0/24	RIPE	Valid

109.207.32.0/24

RIPE

Valid

109.207.40.0/24

RIPE

Valid

109.207.41.0/24

RIPE

Valid

109.207.42.0/24

RIPE

Valid

109.207.43.0/24

RIPE

Valid

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.