bgpreport

Network · data from 2026-11-12

AS2773 DTAG-IOT Deutsche Telekom AG

Registry name: DTAG-IOT Deutsche Telekom AG, DE · not in PeeringDB

47IPv4 routes 87.2% RPKI valid · 100.0% with a route object
5IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
32Route objects not announced registered with origin AS2773, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS2773, 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.
64.43.230.0/24 No ROA RIR databaseARIN 673 100% 67
64.43.231.0/24 No ROA RIR databaseARIN 673 100% 67
64.43.240.0/24 No ROA RIR databaseARIN 673 100% 67
64.43.244.0/24 No ROA RIR databaseARIN 673 100% 67
64.43.250.0/24 No ROA RIR databaseARIN 673 100% 67
64.43.252.0/24 No ROA RIR databaseARIN 673 100% 67
2605:b740:10::/44 No ROA RIR databaseARIN 628 99% 67
2605:b740:40::/42 No ROA RIR databaseARIN 628 99% 67
2605:b740:90::/44 No ROA RIR databaseARIN 628 99% 67
2605:b740:140::/42 No ROA RIR databaseARIN 628 99% 67
2605:b740:100::/42 No ROA RIR databaseARIN 2 0%low visibility 2
164.18.0.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.1.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.2.0/23 Valid RIR databaseRIPE 673 100% 67
164.18.4.0/22 Valid RIR databaseRIPE 673 100% 67
164.18.8.0/22 Valid RIR databaseRIPE 673 100% 67
164.18.12.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.13.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.14.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.15.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.64.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.65.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.128.0/23 Valid RIR databaseRIPE 673 100% 67
164.18.160.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.161.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.162.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.163.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.164.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.165.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.166.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.167.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.168.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.169.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.170.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.171.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.172.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.173.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.174.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.175.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.176.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.177.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.225.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.226.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.227.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.228.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.229.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.230.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.231.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.232.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.233.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.234.0/24 Valid RIR databaseRIPE 673 100% 67
164.18.235.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none11
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none64.43.230.0/24No ROA covers it. Add a ROA for AS2773, maxLength 24.673 of 673
ROA: none64.43.231.0/24No ROA covers it. Add a ROA for AS2773, maxLength 24.673 of 673
ROA: none64.43.240.0/24No ROA covers it. Add a ROA for AS2773, maxLength 24.673 of 673
ROA: none64.43.244.0/24No ROA covers it. Add a ROA for AS2773, maxLength 24.673 of 673
ROA: none64.43.250.0/24No ROA covers it. Add a ROA for AS2773, maxLength 24.673 of 673
ROA: none64.43.252.0/24No ROA covers it. Add a ROA for AS2773, maxLength 24.673 of 673
ROA: none2605:b740:10::/44No ROA covers it. Add a ROA for AS2773, maxLength 44.628 of 636
ROA: none2605:b740:40::/42No ROA covers it. Add a ROA for AS2773, maxLength 42.628 of 636
ROA: none2605:b740:90::/44No ROA covers it. Add a ROA for AS2773, maxLength 44.628 of 636
ROA: none2605:b740:140::/42No ROA covers it. Add a ROA for AS2773, maxLength 42.628 of 636
ROA: none2605:b740:100::/42No ROA covers it. Add a ROA for AS2773, maxLength 42.2 of 636

Route objects not announced

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

164.18.0.0/20RIPENo ROA
164.18.236.0/24RIPENo ROA
164.18.237.0/24RIPENo ROA
164.18.238.0/24RIPENo ROA
164.18.239.0/24RIPENo ROA
2605:3c80:e10::/44ARINNo ROA
2605:b740::/40ARINNo ROA
2605:b740::/42ARINNo ROA
2605:b740::/44ARINNo ROA
2605:b740:20::/44ARINNo ROA
2605:b740:30::/44ARINNo ROA
2605:b740:40::/44ARINNo ROA
2605:b740:50::/44ARINNo ROA
2605:b740:60::/44ARINNo ROA
2605:b740:70::/44ARINNo ROA
2605:b740:80::/42ARINNo ROA
2605:b740:80::/44ARINNo ROA
2605:b740:a0::/44ARINNo ROA
2605:b740:b0::/44ARINNo ROA
2605:b740:c0::/42ARINNo ROA
2605:b740:c0::/44ARINNo ROA
2605:b740:d0::/44ARINNo ROA
2605:b740:e0::/44ARINNo ROA
2605:b740:f0::/44ARINNo ROA
2605:b740:100::/40ARINNo ROA
2605:b740:180::/42ARINNo ROA
2605:b740:1c0::/42ARINNo ROA
2605:b740:200::/40ARINNo ROA
2605:b740:200::/42ARINNo ROA
2605:b740:240::/42ARINNo ROA
2605:b740:280::/42ARINNo ROA
2605:b740:2c0::/42ARINNo 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.