Network · data from 2026-11-12

AS59909 TELE-TEC-AS Tele-Tec GmbH

Registry name: TELE-TEC-AS Tele-Tec GmbH, AT · not in PeeringDB

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

4IPv6 routes 100.0% RPKI valid · 75.0% with a route object

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

14Route objects not announced registered with origin AS59909, seen from no peer

Announced routes

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


2a05:e40:2000::/38	Valid	Nonecovered by 2a05:e40::/29	635 100%	67
168.222.188.0/22	Valid	RIR databaseRIPE	672 100%	66
185.67.108.0/22	Valid	RIR databaseRIPE	672 100%	66
185.67.108.0/24	Valid	RIR databaseRIPE	672 100%	66
185.67.109.0/24	Valid	RIR databaseRIPE	672 100%	66
185.67.110.0/24	Valid	RIR databaseRIPE	672 100%	66
185.67.111.0/24	Valid	RIR databaseRIPE	672 100%	66
45.9.220.0/22	Valid	RIR databaseRIPE	671 100%	67
159.255.147.0/24	Valid	RIR databaseRIPE	671 100%	67
45.9.220.0/24	Valid	RIR databaseRIPE	670 100%	67
45.9.221.0/24	Valid	RIR databaseRIPE	670 100%	67
45.9.222.0/24	Valid	RIR databaseRIPE	670 100%	67
45.9.223.0/24	Valid	RIR databaseRIPE	670 100%	67
2a0d:d100::/32	Valid	RIR databaseRIPE	635 100%	69
2a05:e40::/29	Valid	RIR databaseRIPE	634 100%	69
2a0e:1500::/29	Valid	RIR databaseRIPE	634 100%	69

AS-SET

AS59909 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 15 are in fix.csv.

Route object: none1
Route object: not announced14

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a05:e40:2000::/38	No route object for it. A route object for 2a05:e40::/29 with origin AS59909 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59909 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a05:e40:2000::/38

No route object for it. A route object for 2a05:e40::/29 with origin AS59909 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59909 in the RIR database for the space.

635 of 636

Route objects not announced

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


45.90.76.0/22	RIPE	Valid
45.90.76.0/24	RIPE	Valid
45.90.77.0/24	RIPE	Valid
45.90.78.0/24	RIPE	Valid
45.90.79.0/24	RIPE	Valid
185.67.110.0/23	RIPE	Valid
185.148.92.0/22	RIPE	Valid
199.255.112.0/22	RIPE	Valid
206.225.20.0/22	RIPE	Valid
212.24.116.0/22	RIPE	Valid
2a05:e44::/30	RIPE	Valid
2a0c:b5c0::/29	RIPE	Valid
2a0c:b5c0::/30	RIPE	Valid
2a0c:b5c4::/30	RIPE	Valid

45.90.76.0/22

RIPE

Valid

45.90.76.0/24

RIPE

Valid

45.90.77.0/24

RIPE

Valid

45.90.78.0/24

RIPE

Valid

45.90.79.0/24

RIPE

Valid

185.67.110.0/23

RIPE

Valid

185.148.92.0/22

RIPE

Valid

199.255.112.0/22

RIPE

Valid

206.225.20.0/22

RIPE

Valid

212.24.116.0/22

RIPE

Valid

2a05:e44::/30

RIPE

Valid

2a0c:b5c0::/29

RIPE

Valid

2a0c:b5c0::/30

RIPE

Valid

2a0c:b5c4::/30

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.