Autonomous System Number (ASN)3320
ASN NameDTAG
Organization NameDeutsche Telekom AG
DescriptionInternet service provider operations
Org Handleorg-dta2-ripe
CountryDE
TypeISP
Domain Nametelekom.de
Allocation StatusASSIGNED
HostRIPE
Total IPv4 Routes868
Total IPv6 Routes142
Date Allocated1970-01-01
Route Objects(Total 1010 records)
OriginAS3320
Origin NameDeutsche Telekom AG
ISPDeutsche Telekom AG
Number of IPs1.2089258196146292e+24
OriginAS3320
Origin NameDeutsche Telekom AG
ISPDeutsche Telekom AG
Number of IPs256
OriginAS3320
Origin NameDeutsche Telekom AG
ISPDeutsche Telekom AG
Number of IPs512
Peers(Total 827 records)
OriginChina Unicom Backbone
CountryCN
OriginCornelsen Verlag GmbH
CountryDE
OriginSecurebit AG
CountryCH
Contacts
Abuse Contacts
abuse@telekom.de
Legacy Routes
64.137.125.0/24
84.246.108.0/24
155.117.215.0/24
199.59.232.0/24
194.31.142.0/24
95.155.140.0/24
Whois Response
Statustrue
Whois Serverwhois.ripe.net
AS Blocks
AS BlockAS3209 - AS3353
Description
RIPE NCC ASN block
Remarks
These AS Numbers are assigned to network operators in the RIPE NCC service region.
Maintained By
RIPE-NCC-HM-MNT
Date Created2018-11-22
Date Updated2018-11-22
SourceRIPE
Aut Numbers
Aut NumberAS3320
AS NameDTAG
StatusASSIGNED
Description
Internet service provider operations
MP Import
afi ipv6.unicast from AS-ANY accept ANY
MP Export
afi ipv6.unicast to AS3320:AS-CUSTOMERS-V6 announce ANY
afi ipv6.unicast to AS-ANY announce AS3320:AS-DTAG-V6
OrganizationORG-DTA2-RIPE
Admin Contacts
SB15220-RIPE
Tech Contacts
SB15220-RIPE
Remarks
peering coordinators for AS3320: <peering@telekom.de>
abuse reports should be sent to the contacts listed in the registry entries for the IP address of the offending host system
We 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.
the most important and helpful use of the IRR is to publish what a network will announce to peers and upstream # we are providing that by means of the AS-set AS3320:AS-DTAG which we have been keeping up to date all the time
we 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)
we 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)
in fact we apply route filters based on this for all neighbors - as far as feasible
for data published through the RIPE routing registry we generate filters automatically
we consider the integration of RIR and routing registry data and the application of RPSS authorization a great feature of the RIPE routing registry # unfortunately this benefit is not available with any other IRR database that we know of... and some of the IRR databases allow essentially any garbage to be registered without any control - making those databases quite useless...
customers 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)
this will be sufficient to have our peers accept the routes
in any case peers - and any network in the Internet - is free to apply some selective policy (e.g. prefix length based) # but we do not think that any such selective policy will be based on details of our routing policy omitted from this aut-num: object
unfortunately 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
we 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
============================================================== IPv6 we do/publish essentially the same like for IPv4
==============================================================
Maintained By
RIPE-NCC-END-MNT
DTAG-RR
Date Created1970-01-01
Date Updated2020-12-11
SourceRIPE
Organization Details
TypeLIR
HandleORG-DTA2-RIPE
NameDeutsche Telekom AG
Address
Eduard-Schopf-Allee 1
D-28217
Bremen
GERMANY
Abuse Contacts
DTAG3-RIPE
Phone
+4942151554041
+4942151555165
Fax No
+49391580100379
+494412344589
Admin Contacts
DTAG-RIPE
SL7866-RIPE
EH4097-RIPE
SB15220-RIPE
Maintained By
RIPE-NCC-HM-MNT
DTAG-NIC
Maintained Ref
RIPE-NCC-HM-MNT
DTAG-NIC
Country
DE
Date Created2004-04-17
Date Updated2026-02-05
SourceRIPE
Administrative Contacts
HandleSB15220-RIPE
NameSebastian Becker
CountryDEUTSCHLAND
Address
Deutsche Telekom AG
Wolbecker Str. 268, 48155, Muenster, Deutschland
Phone
+49 228 18123797
Maintained By
DTAG-NIC
DTAG-RR
Date Created2011-11-01
Date Updated2024-09-03
SourceRIPE
Technical Contacts
HandleSB15220-RIPE
NameSebastian Becker
CountryDEUTSCHLAND
Address
Deutsche Telekom AG
Wolbecker Str. 268, 48155, Muenster, Deutschland
Phone
+49 228 18123797
Maintained By
DTAG-NIC
DTAG-RR
Date Created2011-11-01
Date Updated2024-09-03
SourceRIPE
