Network · data from 2026-11-12

AS41789 TELEDYNE-AS LLC Teledyne Systems Limited

Registry name: TELEDYNE-AS LLC Teledyne Systems Limited, RU · not in PeeringDB

65IPv4 routes 98.5% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

6Route objects not announced registered with origin AS41789, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41789, 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.247.190.0/24	No ROA	RIR databaseRIPE	673 100%	66
31.129.0.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.1.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.2.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.3.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.4.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.5.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.6.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.7.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.8.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.9.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.10.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.11.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.12.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.13.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.14.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.15.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.16.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.17.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.18.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.19.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.20.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.23.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.24.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.25.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.26.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.27.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.28.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.29.0/24	Valid	RIR databaseRIPE	673 100%	66
31.129.31.0/24	Valid	RIR databaseRIPE	673 100%	66
46.16.8.0/24	Valid	RIR databaseRIPE	673 100%	66
46.16.9.0/24	Valid	RIR databaseRIPE	673 100%	66
46.16.10.0/24	Valid	RIR databaseRIPE	673 100%	66
46.16.11.0/24	Valid	RIR databaseRIPE	673 100%	66
46.227.24.0/24	Valid	RIR databaseRIPE	673 100%	66
46.227.25.0/24	Valid	RIR databaseRIPE	673 100%	66
46.227.26.0/24	Valid	RIR databaseRIPE	673 100%	66
46.227.27.0/24	Valid	RIR databaseRIPE	673 100%	66
46.227.28.0/24	Valid	RIR databaseRIPE	673 100%	66
46.227.29.0/24	Valid	RIR databaseRIPE	673 100%	66
46.227.30.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.144.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.145.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.146.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.147.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.148.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.149.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.150.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.151.0/24	Valid	RIR databaseRIPE	673 100%	66
91.142.152.0/21	Valid	RIR databaseRIPE	673 100%	66
91.142.158.0/24	Valid	RIR databaseRIPE	673 100%	66
159.255.0.0/20	Valid	RIR databaseRIPE	673 100%	66
159.255.28.0/24	Valid	RIR databaseRIPE	673 100%	66
159.255.30.0/24	Valid	RIR databaseRIPE	673 100%	66
159.255.31.0/24	Valid	RIR databaseRIPE	673 100%	66
159.255.16.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.17.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.18.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.19.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.20.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.21.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.22.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.23.0/24	Valid	RIR databaseRIPE	672 100%	66
159.255.29.0/24	Valid	RIR databaseRIPE	672 100%	66
46.227.31.0/24	Valid	RIR databaseRIPE	670 100%	66

AS-SET

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

ROA: none1
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
ROA: none	91.247.190.0/24	No ROA covers it. Add a ROA for AS41789, maxLength 24.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

91.247.190.0/24

No ROA covers it. Add a ROA for AS41789, maxLength 24.

673 of 673

Route objects not announced

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


31.129.0.0/20	RIPE	Valid
46.16.8.0/22	RIPE	No ROA
46.227.24.0/21	RIPE	No ROA
91.142.144.0/20	RIPE	No ROA
159.255.16.0/21	RIPE	No ROA
159.255.28.0/22	RIPE	No ROA

31.129.0.0/20

RIPE

Valid

46.16.8.0/22

RIPE

No ROA

46.227.24.0/21

RIPE

No ROA

91.142.144.0/20

RIPE

No ROA

159.255.16.0/21

RIPE

No ROA

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