Network · data from 2026-11-12

AS6878 AS6878 T-Systems International GmbH

Registry name: AS6878 T-Systems International GmbH, DE · not in PeeringDB

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

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

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

20Route objects not announced registered with origin AS6878, seen from no peer

Announced routes

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


80.158.0.0/23	Valid	RIR databaseRIPE	673 100%	67
80.158.24.0/21	Valid	RIR databaseRIPE	673 100%	67
80.158.76.0/23	Valid	RIR databaseRIPE	673 100%	67
80.158.78.0/23	Valid	RIR databaseRIPE	673 100%	67
80.158.88.0/22	Valid	RIR databaseRIPE	673 100%	67
80.158.104.0/21	Valid	RIR databaseRIPE	673 100%	67
160.44.192.0/21	Valid	RIR databaseRIPE	673 100%	67
160.44.200.0/21	Valid	RIR databaseRIPE	673 100%	67
164.30.0.0/19	Valid	RIR databaseRIPE	673 100%	67
164.30.32.0/21	Valid	RIR databaseRIPE	673 100%	67
164.30.44.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.45.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.46.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.47.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.60.0/22	Valid	RIR databaseRIPE	673 100%	67
164.30.63.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.64.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.65.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.66.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.67.0/24	Valid	RIR databaseRIPE	673 100%	67
164.30.68.0/22	Valid	RIR databaseRIPE	673 100%	67
164.30.72.0/22	Valid	RIR databaseRIPE	673 100%	67
164.30.79.0/24	Valid	RIR databaseRIPE	673 100%	67
46.29.96.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.2.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.24.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.25.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.26.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.27.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.31.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.72.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.73.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.74.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.75.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.80.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.81.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.82.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.83.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.84.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.85.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.92.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.93.0/24	Valid	RIR databaseRIPE	672 100%	67
80.158.97.0/24	Valid	RIR databaseRIPE	672 100%	68
80.158.0.0/21	Valid	RIR databaseRIPE	671 100%	67
80.158.32.0/20	Valid	RIR databaseRIPE	671 100%	67
80.158.48.0/20	Valid	RIR databaseRIPE	671 100%	67
93.188.242.0/24	Valid	RIR databaseRIPE	671 100%	67
80.158.16.0/21	Valid	RIR databaseRIPE	670 100%	67
2a00:da8:fffb::/48	Valid	RIR databaseRIPE	629 99%	67
2a07:b980:4010::/44	Valid	RIR databaseRIPE	623 98%	67
2a07:b980:4030::/44	Valid	RIR databaseRIPE	623 98%	67

AS-SET

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

Route object: not announced20

Route objects not announced

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


80.158.16.0/20	RIPE	Valid
80.158.32.0/19	RIPE	Valid
80.158.48.0/24	RIPE	Valid
80.158.72.0/21	RIPE	Valid
80.158.72.0/22	RIPE	Valid
80.158.80.0/20	RIPE	Valid
80.158.84.0/23	RIPE	Valid
80.158.96.0/19	RIPE	Valid
80.158.96.0/22	RIPE	Valid
80.158.96.0/24	RIPE	Valid
80.158.98.0/23	RIPE	Valid
80.158.100.0/22	RIPE	Valid
164.30.0.0/17	RIPE	Valid
164.30.48.0/22	RIPE	Valid
2a07:b980:4000::/39	RIPE	Valid
2a07:b980:4000::/44	RIPE	Valid
2a07:b980:4020::/44	RIPE	Valid
2a07:b980:4040::/44	RIPE	Valid
2a07:b980:4050::/44	RIPE	Valid
2a07:b980:4060::/44	RIPE	Valid

80.158.16.0/20

RIPE

Valid

80.158.32.0/19

RIPE

Valid

80.158.48.0/24

RIPE

Valid

80.158.72.0/21

RIPE

Valid

80.158.72.0/22

RIPE

Valid

80.158.80.0/20

RIPE

Valid

80.158.84.0/23

RIPE

Valid

80.158.96.0/19

RIPE

Valid

80.158.96.0/22

RIPE

Valid

80.158.96.0/24

RIPE

Valid

80.158.98.0/23

RIPE

Valid

80.158.100.0/22

RIPE

Valid

164.30.0.0/17

RIPE

Valid

164.30.48.0/22

RIPE

Valid

2a07:b980:4000::/39

RIPE

Valid

2a07:b980:4000::/44

RIPE

Valid

2a07:b980:4020::/44

RIPE

Valid

2a07:b980:4040::/44

RIPE

Valid

2a07:b980:4050::/44

RIPE

Valid

2a07:b980:4060::/44

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.