whatsmyip.fyi
Tools

AS3320 DTAG Deutsche Telekom AG

Everything the routing table and the registries say about AS3320: who holds it, which registry issued it, and which address blocks it advertises.

Consumer and business ISPsAS3320

915 IPv4 and 45 IPv6 prefixes announced.

Registry facts

Refreshed daily
AS number
AS3320
Holder
DTAG Deutsche Telekom AG
Country
Not published
Regional registry
RIPE — RIPE Network Coordination Centre
Registry block
3154-3353 (IANA 16-bit Autonomous System (AS) Numbers Registry)
Announced today
Yes
IPv4 prefixes
915
IPv6 prefixes
45
Observed at
2026-09-05T16:00:00

Data: RIPEstat. Prefix and holder data comes from the RIPEstat Data API and is cached for 24 hours. The regional registry is derived from the IANA AS number allocation table. Authoritative registry records are served by RIPE RDAP.

Announced prefixes

915 IPv4 · 45 IPv6
  • 155 IPv4 shown
  • 45 IPv6 shown
  • 2.58.100.0/24
  • 2.58.102.0/24
  • 2.160.0.0/12
  • 5.133.112.0/24
  • 5.182.153.0/24
  • 5.249.188.0/22
  • 13.143.122.0/24
  • 31.56.72.0/24
  • 31.56.76.0/24
  • 31.56.90.0/24
  • 31.57.54.0/24
  • 31.57.119.0/24
  • 31.59.71.0/24
  • 31.59.167.0/24
  • 31.59.224.0/24
  • 31.59.225.0/24
  • 31.59.226.0/24
  • 31.59.227.0/24
  • 31.212.0.0/15
  • 31.224.0.0/11
  • 37.46.11.0/24
  • 37.50.0.0/15
  • 37.80.0.0/12
  • 43.251.0.0/22
  • 45.93.186.0/23
  • 45.129.165.0/24
  • 45.145.16.0/24
  • 45.147.227.0/24
  • 45.151.112.0/23
  • 45.151.114.0/23
  • 45.157.32.0/23
  • 45.159.192.0/23
  • 46.78.0.0/15
  • 46.80.0.0/12
  • 51.146.22.0/24
  • 51.146.74.0/24
  • 51.194.221.0/24
  • 51.241.18.0/24
  • 51.241.86.0/24
  • 51.241.133.0/24
  • 51.241.228.0/22
  • 62.56.208.0/21
  • 62.112.30.0/24
  • 62.153.0.0/16
  • 62.154.0.0/15
  • 62.156.0.0/14
  • 62.192.100.0/23
  • 62.192.106.0/23
  • 62.224.0.0/14
  • 62.244.46.0/24
  • 64.8.232.0/23
  • 64.49.56.0/22
  • 64.105.212.0/23
  • 64.105.214.0/23
  • 64.105.216.0/23
  • 64.105.220.0/23
  • 64.105.222.0/23
  • 64.105.234.0/23
  • 64.105.236.0/23
  • 64.137.34.0/23
  • 64.137.40.0/23
  • 64.137.119.0/24
  • 64.137.125.0/24
  • 64.137.127.0/24
  • 64.139.32.0/23
  • 64.139.34.0/23
  • 68.167.158.0/23
  • 77.83.136.0/23
  • 77.83.138.0/23
  • 78.105.116.0/24
  • 78.105.146.0/24
  • 78.105.204.0/24
  • 79.121.129.0/24
  • 79.121.131.0/24
  • 79.121.137.0/24
  • 79.121.146.0/24
  • 79.121.170.0/24
  • 79.121.172.0/24
  • 79.121.175.0/24
  • 79.121.182.0/24
  • 79.121.197.0/24
  • 79.121.199.0/24
  • 79.121.210.0/24
  • 79.121.221.0/24
  • 79.121.225.0/24
  • 79.121.229.0/24
  • 79.121.230.0/24
  • 79.121.236.0/24
  • 79.121.240.0/24
  • 79.121.243.0/24
  • 79.121.245.0/24
  • 79.121.248.0/24
  • 79.121.250.0/24
  • 79.121.255.0/24
  • 79.192.0.0/10
  • 80.64.240.0/22
  • 80.71.231.0/24
  • 80.83.80.0/21
  • 80.128.0.0/11
  • 80.128.0.0/12
  • 80.144.0.0/13
  • 80.152.0.0/14
  • 80.156.0.0/16
  • 80.157.0.0/16
  • 80.157.8.0/21
  • 80.157.16.0/20
  • 80.187.0.0/16
  • 80.187.160.0/20
  • 81.199.64.0/21
  • 81.199.72.0/21
  • 81.201.32.0/20
  • 82.21.184.0/24
  • 82.22.105.0/24
  • 82.22.108.0/24
  • 82.22.191.0/24
  • 82.22.194.0/24
  • 82.23.168.0/24
  • 82.23.228.0/24
  • 82.24.14.0/24
  • 82.24.30.0/24
  • 82.24.55.0/24
  • 82.24.78.0/24
  • 82.24.109.0/24
  • 82.24.114.0/24
  • 82.24.125.0/24
  • 82.25.24.0/24
  • 82.25.133.0/24
  • 82.25.191.0/24
  • 82.25.197.0/24
  • 82.25.202.0/24
  • 82.26.70.0/24
  • 82.26.100.0/24
  • 82.26.108.0/24
  • 82.26.111.0/24
  • 82.26.123.0/24
  • 82.26.128.0/24
  • 82.26.135.0/24
  • 82.26.161.0/24
  • 82.26.168.0/24
  • 82.27.10.0/24
  • 82.27.22.0/24
  • 82.27.198.0/24
  • 82.29.23.0/24
  • 82.29.29.0/24
  • 82.29.120.0/24
  • 82.38.102.0/24
  • 82.38.111.0/24
  • 82.38.133.0/24
  • 82.38.220.0/24
  • 82.38.221.0/24
  • 82.38.222.0/24
  • 82.39.102.0/24
  • 82.39.254.0/24
  • 82.39.255.0/24
  • 82.40.21.0/24
  • 2001:650:cc02::/48
  • 2001:678:1038::/48
  • 2001:678:36c::/48
  • 2001:678:5b0::/48
  • 2001:678:5d4::/48
  • 2001:678:a04::/48
  • 2001:678:adc::/48
  • 2001:678:b1c::/48
  • 2001:678:bdc::/48
  • 2001:678:d4c::/48
  • 2001:678:ff0::/48
  • 2001:67c:11a4::/48
  • 2001:67c:227c::/48
  • 2001:67c:22d4::/48
  • 2001:67c:2d88::/48
  • 2001:67c:2e28::/48
  • 2001:67c:5cc::/48
  • 2001:67c:94c::/48
  • 2001:67c:b80::/48
  • 2001:67c:c9c::/48
  • 2001:67c:ec0::/48
  • 2003::/19
  • 2003:8:f517::/48
  • 2602:fd92:c60::/44
  • 2a00:5c60:3::/48
  • 2a00:5c60:a::/48
  • 2a00:6680::/47
  • 2a00:6680:2::/47
  • 2a01:598::/29
  • 2a03:1e80:c000::/40
  • 2a03:5ee0::/32
  • 2a05:1240:2::/48
  • 2a05:1240:3::/48
  • 2a05:1240:4::/48
  • 2a05:1240:5::/48
  • 2a05:1240:6::/48
  • 2a09:6f80::/29
  • 2a09:8180::/30
  • 2a0a:5340:ffff::/48
  • 2a0e:4c44:5410::/48
  • 2a0e:901:d001::/48
  • 2a10:cd80::/29
  • 2a11:7400:d1::/48
  • 2a12:6900:1000::/40
  • 2a14:9600::/29

A prefix here is a block this AS was seen originating in BGP, not a block it is guaranteed to own. Announcement and allocation are different facts, and they disagree more often than people expect.

Registry record

ripe
FieldValue
aut-num3320
as-nameDTAG
orgORG-DTA2-RIPE
descrInternet service provider operations
remarkspeering coordinators for AS3320:
remarksabuse reports should be sent to the contacts listed in the registry entries for the IP address of the offending host system
remarksWe share the view that for many networks (including ours:-) only some abstraction of the actual routing policy should/can be published in the IRR. Right now we are abstracting to a very essential minimum.
remarksthe most important and helpful use of the IRR is to publish what a network will announce to peers and upstream
remarkswe encourage all our neighbors to define and maintain an AS-set to describe their announcements, and to register all the routes (and have their customers do so as well)
importfrom AS-ANY accept ANY
remarkswe maintain a list of what our neighbors have told us about their announcements towards AS3320 - in terms of AS-set (preferred), AS number, route-set (and the IRR database used to publish)
remarksin fact we apply route filters based on this for all neighbors - as far as feasible
remarksfor data published through the RIPE routing registry we generate filters automatically
remarkswe consider the integration of RIR and routing registry data and the application of RPSS authorization a great feature of the RIPE routing registry
exportto AS3320:AS-CUSTOMERS announce ANY
exportto AS-ANY announce AS3320:AS-DTAG
remarkscustomers are strongly encouraged to define and maintain an AS-set that we will include in the definition of AS3320:AS-DTAG (if we are told the name)
remarksthis will be sufficient to have our peers accept the routes
remarksin any case peers - and any network in the Internet - is free to apply some selective policy (e.g. prefix length based)
remarksunfortunately some customers do not provide usable IRR data; we will NOT add to the uncontrolled garbage in the IRR by proxy registering in some database that requires no authorization
remarkswe advise customers that routes without IRR registration and not covered by AS3320:AS-DTAG may receive less than full support by some of our peer networks and other parts of the Internet
remarks============================================================== IPv6 we do/publish essentially the same like for IPv4
mp-importafi ipv6.unicast from AS-ANY accept ANY
mp-exportafi ipv6.unicast to AS3320:AS-CUSTOMERS-V6 announce ANY

Next