Network · data from 2026-11-12

AS48951 ASN-TSI-IAS Telekom Deutschland GmbH

Registry name: ASN-TSI-IAS Telekom Deutschland GmbH, DE · not in PeeringDB

27IPv4 routes 100.0% RPKI valid · 92.6% with a route object

11IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

31Route objects not announced registered with origin AS48951, seen from no peer

Announced routes

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


185.149.164.0/22	Valid	Other origin only	673 100%	67
194.41.39.0/24	Valid	Other origin only	673 100%	67
78.140.64.0/24	Valid	RIR databaseRIPE	673 100%	67
78.140.65.0/24	Valid	RIR databaseRIPE	673 100%	67
78.140.66.0/24	Valid	RIR databaseRIPE	673 100%	67
78.140.72.0/24	Valid	RIR databaseRIPE	673 100%	67
81.7.208.0/21	Valid	RIR databaseRIPE	673 100%	67
81.7.208.0/22	Valid	RIR databaseRIPE	673 100%	67
81.7.216.0/21	Valid	RIR databaseRIPE	673 100%	67
81.7.216.0/22	Valid	RIR databaseRIPE	673 100%	67
81.7.220.0/22	Valid	RIR databaseRIPE	673 100%	67
82.210.224.0/19	Valid	RIR databaseRIPE	673 100%	67
82.210.254.0/24	Valid	RIR databaseRIPE	673 100%	67
82.210.255.0/24	Valid	RIR databaseRIPE	673 100%	67
93.122.0.0/17	Valid	RIR databaseRIPE	673 100%	67
93.122.40.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.44.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.56.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.60.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.64.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.68.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.72.0/21	Valid	RIR databaseRIPE	673 100%	67
93.122.80.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.84.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.88.0/22	Valid	RIR databaseRIPE	673 100%	67
93.122.92.0/22	Valid	RIR databaseRIPE	673 100%	67
78.140.76.0/24	Valid	RIR databaseRIPE	671 100%	67
2a01:667:400::/40	Valid	RIR databaseRIPE	634 100%	70
2a01:666:400::/40	Valid	RIR databaseRIPE	628 99%	67
2a01:660::/29	Valid	RIR databaseRIPE	627 99%	67
2a01:664:800::/38	Valid	RIR databaseRIPE	627 99%	67
2a01:664:1800::/40	Valid	RIR databaseRIPE	627 99%	67
2a01:666::/40	Valid	RIR databaseRIPE	627 99%	67
2a01:666::/32	Valid	RIR databaseRIPE	626 98%	67
2a01:664:1900::/40	Valid	RIR databaseRIPE	3 0%low visibility	3
2a01:667::/32	Valid	RIR databaseRIPE	3 0%low visibility	4
2a01:667::/40	Valid	RIR databaseRIPE	3 0%low visibility	4
2a01:664::/38	Valid	RIR databaseRIPE	1 0%low visibility	1

185.149.164.0/22

Valid

Other origin only

673 100%

194.41.39.0/24

Valid

Other origin only

673 100%

78.140.64.0/24

Valid

RIR databaseRIPE

673 100%

78.140.65.0/24

Valid

RIR databaseRIPE

673 100%

78.140.66.0/24

Valid

RIR databaseRIPE

673 100%

78.140.72.0/24

Valid

RIR databaseRIPE

673 100%

81.7.208.0/21

Valid

RIR databaseRIPE

673 100%

81.7.208.0/22

Valid

RIR databaseRIPE

673 100%

81.7.216.0/21

Valid

RIR databaseRIPE

673 100%

81.7.216.0/22

Valid

RIR databaseRIPE

673 100%

81.7.220.0/22

Valid

RIR databaseRIPE

673 100%

82.210.224.0/19

Valid

RIR databaseRIPE

673 100%

82.210.254.0/24

Valid

RIR databaseRIPE

673 100%

82.210.255.0/24

Valid

RIR databaseRIPE

673 100%

93.122.0.0/17

Valid

RIR databaseRIPE

673 100%

93.122.40.0/22

Valid

RIR databaseRIPE

673 100%

93.122.44.0/22

Valid

RIR databaseRIPE

673 100%

93.122.56.0/22

Valid

RIR databaseRIPE

673 100%

93.122.60.0/22

Valid

RIR databaseRIPE

673 100%

93.122.64.0/22

Valid

RIR databaseRIPE

673 100%

93.122.68.0/22

Valid

RIR databaseRIPE

673 100%

93.122.72.0/21

Valid

RIR databaseRIPE

673 100%

93.122.80.0/22

Valid

RIR databaseRIPE

673 100%

93.122.84.0/22

Valid

RIR databaseRIPE

673 100%

93.122.88.0/22

Valid

RIR databaseRIPE

673 100%

93.122.92.0/22

Valid

RIR databaseRIPE

673 100%

78.140.76.0/24

Valid

RIR databaseRIPE

671 100%

2a01:667:400::/40

Valid

RIR databaseRIPE

634 100%

2a01:666:400::/40

Valid

RIR databaseRIPE

628 99%

2a01:660::/29

Valid

RIR databaseRIPE

627 99%

2a01:664:800::/38

Valid

RIR databaseRIPE

627 99%

2a01:664:1800::/40

Valid

RIR databaseRIPE

627 99%

2a01:666::/40

Valid

RIR databaseRIPE

627 99%

2a01:666::/32

Valid

RIR databaseRIPE

626 98%

2a01:664:1900::/40

Valid

RIR databaseRIPE

3 0%low visibility

2a01:667::/32

Valid

RIR databaseRIPE

3 0%low visibility

2a01:667::/40

Valid

RIR databaseRIPE

3 0%low visibility

2a01:664::/38

Valid

RIR databaseRIPE

1 0%low visibility

AS-SET

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

Route object: none2
Route object: not announced31

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.149.164.0/22	Route objects for it name AS20570. Add a route object with origin AS48951 in the RIR database for the space.	673 of 673
Route object: none	194.41.39.0/24	Route objects for it name AS20570. Add a route object with origin AS48951 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.149.164.0/22

Route objects for it name AS20570. Add a route object with origin AS48951 in the RIR database for the space.

673 of 673

Route object: none

194.41.39.0/24

Route objects for it name AS20570. Add a route object with origin AS48951 in the RIR database for the space.

673 of 673

Route objects not announced

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


64.43.250.0/24	RIPE-NONAUTH	No ROA
78.140.64.0/18	RIPE	Valid
78.140.64.0/21	RIPE	Valid
78.140.67.0/24	RIPE	Valid
78.140.68.0/24	RIPE	Valid
78.140.72.0/22	RIPE	Valid
78.140.76.0/22	RIPE	Valid
78.140.80.0/23	RIPE	Valid
78.140.80.0/24	RIPE	Valid
78.140.81.0/24	RIPE	Valid
81.7.192.0/19	RIPE	Valid
82.210.192.0/18	RIPE	Valid
93.122.48.0/22	RIPE	Valid
93.122.52.0/22	RIPE	Valid
141.78.100.0/24	RIPE	No ROA
141.78.101.0/24	RIPE	No ROA
141.78.102.0/24	RIPE	No ROA
141.78.103.0/24	RIPE	No ROA
142.39.240.0/20	RIPE-NONAUTH	No ROA
193.102.158.0/23	RIPE	No ROA
193.102.172.0/23	RIPE	No ROA
195.114.22.0/24	RIPE	No ROA
195.114.23.0/24	RIPE	No ROA
2a01:664:1::/48	RIPE	Invalid: maxLength
2a01:664:1200::/39	RIPE	Valid
2a01:664:1200::/40	RIPE	Valid
2a01:664:1300::/40	RIPE	Valid
2a01:664:1600::/40	RIPE	Valid
2a01:664:1700::/40	RIPE	Valid
2a01:664:1a00::/40	RIPE	Valid
2a0b:9a40::/29	RIPE	No ROA

64.43.250.0/24

RIPE-NONAUTH

No ROA

78.140.64.0/18

RIPE

Valid

78.140.64.0/21

RIPE

Valid

78.140.67.0/24

RIPE

Valid

78.140.68.0/24

RIPE

Valid

78.140.72.0/22

RIPE

Valid

78.140.76.0/22

RIPE

Valid

78.140.80.0/23

RIPE

Valid

78.140.80.0/24

RIPE

Valid

78.140.81.0/24

RIPE

Valid

81.7.192.0/19

RIPE

Valid

82.210.192.0/18

RIPE

Valid

93.122.48.0/22

RIPE

Valid

93.122.52.0/22

RIPE

Valid

141.78.100.0/24

RIPE

No ROA

141.78.101.0/24

RIPE

No ROA

141.78.102.0/24

RIPE

No ROA

141.78.103.0/24

RIPE

No ROA

142.39.240.0/20

RIPE-NONAUTH

No ROA

193.102.158.0/23

RIPE

No ROA

193.102.172.0/23

RIPE

No ROA

195.114.22.0/24

RIPE

No ROA

195.114.23.0/24

RIPE

No ROA

2a01:664:1::/48

RIPE

Invalid: maxLength

2a01:664:1200::/39

RIPE

Valid

2a01:664:1200::/40

RIPE

Valid

2a01:664:1300::/40

RIPE

Valid

2a01:664:1600::/40

RIPE

Valid

2a01:664:1700::/40

RIPE

Valid

2a01:664:1a00::/40

RIPE

Valid

2a0b:9a40::/29

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.