bgpreport

Network · data from 2026-11-12

AS21263 TeleData GmbH

Registry name: TELEDATA-AS TeleData GmbH, DE · PeeringDB

39IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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
0Route objects not announced registered with origin AS21263, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21263, 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.
5.104.144.0/21 Valid RIR databaseRIPE 673 100% 66
5.154.177.0/24 Valid RIR databaseRIPE 673 100% 66
5.154.178.0/24 Valid RIR databaseRIPE 673 100% 66
5.154.226.0/23 Valid RIR databaseRIPE 673 100% 66
5.154.230.0/23 Valid RIR databaseRIPE 673 100% 66
45.10.98.0/23 Valid RIR databaseRIPE 673 100% 66
45.155.112.0/22 Valid RIR databaseRIPE 673 100% 66
77.81.52.0/22 Valid RIR databaseRIPE 673 100% 66
81.27.112.0/20 Valid RIR databaseRIPE 673 100% 66
91.196.200.0/22 Valid RIR databaseRIPE 673 100% 66
91.209.197.0/24 Valid RIR databaseRIPE 673 100% 66
146.255.112.0/22 Valid RIR databaseRIPE 673 100% 66
158.94.168.0/24 Valid RIR databaseRIPE 673 100% 66
161.51.240.0/21 Valid RIR databaseRIPE 673 100% 66
178.157.80.0/23 Valid RIR databaseRIPE 673 100% 66
178.157.83.0/24 Valid RIR databaseRIPE 673 100% 66
178.157.88.0/23 Valid RIR databaseRIPE 673 100% 66
185.4.232.0/22 Valid RIR databaseRIPE 673 100% 66
185.16.72.0/22 Valid RIR databaseRIPE 673 100% 66
185.68.188.0/24 Valid RIR databaseRIPE 673 100% 66
185.124.220.0/22 Valid RIR databaseRIPE 673 100% 66
185.124.224.0/22 Valid RIR databaseRIPE 673 100% 66
185.159.244.0/24 Valid RIR databaseRIPE 673 100% 66
185.162.220.0/22 Valid RIR databaseRIPE 673 100% 66
185.198.140.0/22 Valid RIR databaseRIPE 673 100% 66
185.231.72.0/22 Valid RIR databaseRIPE 673 100% 66
188.119.150.0/23 Valid RIR databaseRIPE 673 100% 66
188.119.152.0/24 Valid RIR databaseRIPE 673 100% 66
188.137.184.0/21 Valid RIR databaseRIPE 673 100% 66
192.81.121.0/24 Valid RIR databaseRIPE 673 100% 66
193.39.67.0/24 Valid RIR databaseRIPE 673 100% 66
193.102.75.0/24 Valid RIR databaseRIPE 673 100% 66
194.0.220.0/24 Valid RIR databaseRIPE 673 100% 66
212.62.192.0/19 Valid RIR databaseRIPE 673 100% 66
217.11.144.0/20 Valid RIR databaseRIPE 673 100% 66
217.24.192.0/20 Valid RIR databaseRIPE 673 100% 66
217.31.208.0/20 Valid RIR databaseRIPE 673 100% 66
217.73.152.0/21 Valid RIR databaseRIPE 673 100% 66
128.0.35.0/24 Valid RIR databaseRIPE 672 100% 66
2a0e:1d00::/32 Valid RIR databaseRIPE 635 100% 69
2a01:76c0::/29 Valid RIR databaseRIPE 634 100% 69
2a02:590::/29 Valid RIR databaseRIPE 634 100% 69
2a05:7ac0::/29 Valid RIR databaseRIPE 634 100% 69
2a0c:7780::/29 Valid RIR databaseRIPE 634 100% 69
2a0d:9600::/29 Valid RIR databaseRIPE 634 100% 69
2a13:780::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS21263: RIPE::AS-TELEDATA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS21263 isn't in the set, or no route object for AS21263 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS21263 in itNot covered
RIPE::AS-TELEDATA RIPE 14886 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS21263 is announced.

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.