Telefonica Germany IP Ranges
Telefonica Germany runs the O2 network, and AS6805 is the number its traffic leaves under, assigned by RIPE with the as-name TDDE-ASN1 under the organisation object ORG-TDG4-RIPE. The allocations behind it still carry netnames beginning DE-MEDIAWAYS, after mediaWays GmbH, the Bertelsmann internet subsidiary Telefonica completed the purchase of in January 2001: 77.176.0.0/12 was created on 17 November 2006 as DE-MEDIAWAYS-20061117. The company's own PeeringDB entry still describes itself as former Telefonica Deutschland, former mediaWays GmbH.
- Provider
- Telefonica Germany
- Primary ASN
- AS6805
- Category
- ISP
- Headquarters
- Munich, Germany
- Announced IPv4 prefixes
- 32
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS6805 (TDDE-ASN1 Telefonica Germany GmbH & Co.OHG). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
77.176.0.0/12
77.0.0.0/12
85.176.0.0/13
78.48.0.0/13
217.184.0.0/13
93.128.0.0/13
176.0.0.0/13
92.224.0.0/13
2.240.0.0/13
2.208.0.0/13
2a02:3000::/23
2a01:c00::/26
2001:1a28::/32 (IPv6)
What does a Telefonica Germany IP mean in a privacy test?
An AS6805 address means the traffic left through O2 Germany, and the useful follow-up is which O2 product carried it, because they do not behave alike. On the cable product an O2 moderator states flatly that every o2 my Home connection running over a cable connection has DS-Lite active and that no switch to dual-stack is offered: the line gets IPv6 and reaches IPv4 through a tunnel, so the address a site records is a shared carrier endpoint rather than the household. That statement is scoped to cable and O2 does not extend it to the DSL and fibre lines on the same ASN, which is exactly why the number alone settles nothing. On mobile, a routable IPv4 is not what a line gets by default: it is a chargeable one-off that support enables before the subscriber changes the APN to netpublic and waits for a confirmation message. So one ASN covers an address shared by thousands of cable households and an address belonging to a single line, and only the block it came from tells you which.
What Telefonica Germany publishes about this space
There is no geofeed and no customer-facing allowlist here, so the machine-readable trail is the routing registry rather than a file on the operator's own site. The RIPE allocations sit under the organisation object ORG-TDG4-RIPE and carry MDA-Z as both mnt-by and mnt-lower, and the useful detail is in the netname: each block reads DE-MEDIAWAYS followed by the date the object was created, so DE-MEDIAWAYS-20061117 and DE-MEDIAWAYS-20110513 date the two largest allocations without a separate lookup. The route objects covering them carry the descr Telefonica Germany GmbH & Co. OHG with origin 6805, and one of them keeps a bare remarks: netname: DE-MEDIAWAYS line as well.
For filtering, the set to use is the IRR AS-SET AS-TDDE, which is what the company's own PeeringDB record nominates; that record also classes the network as an NSP with European scope and an open peering policy, and leaves both the policy URL and the looking-glass field empty. What none of it gives you is location. There is no city, no region and no per-product split anywhere in the registry, so nothing at the whois layer distinguishes a cable block from a DSL, fibre or mobile one, and any city a geolocation service shows for an O2 address is that service's inference rather than a statement by Telefonica Germany.
Telling an O2 subscriber from the tunnel endpoint
This is access space, not rented compute, so the split that matters is not operator versus customer but which access product the address belongs to. On cable, DS-Lite means the subscriber holds no public IPv4 at all and inbound IPv4 to that household is structurally impossible; the address a site logs is the carrier's tunnel endpoint and is shared. On mobile the exception is visible in the configuration: a subscriber who paid the one-off charge and set the APN to netpublic gets a routable address out of O2 pools such as 46.114.0.0/15, which AS6805 originates, and everyone who did not is behind the carrier's translation. The O2 statement about DS-Lite names cable connections specifically and stops there, so treat the DSL and fibre side as an open question the covering block has to answer.
The other thing to check is which of the company's two numbers you are on, and the answer has changed. AS13184 is registered to the same company under the holder string HANSENET Telefonica Germany GmbH & Co.OHG, but RIPEstat currently reports it as announcing nothing: its announced flag is false. What survives of it is inside AS6805's own routing policy, which still carries a bidirectional import and export of ANY with AS13184. So a lookup that names 13184 for a German address is reading a registration rather than a live origin, and the covering route object under origin 6805 is the answer that holds.
Related tools
Frequently asked questions
What IP ranges does Telefonica Germany use?
They are announced under AS6805, assigned by RIPE with the as-name TDDE-ASN1 under ORG-TDG4-RIPE. In the RIPE database the blocks appear under netnames beginning DE-MEDIAWAYS, each stamped with the date the object was created, and the IRR set to filter on is AS-TDDE. A second Telefonica Germany number, AS13184, holds the former HanseNet registration but currently announces nothing.
Why does an O2 Germany IP appear in my privacy test?
An AS6805 address means the traffic left through O2 Germany, and the useful follow-up is which O2 product carried it, because they do not behave alike. On the cable product an O2 moderator states flatly that every o2 my Home connection running over a cable connection has DS-Lite active and that no switch to dual-stack is offered: the line gets IPv6 and reaches IPv4 through a tunnel, so the address a site records is a shared carrier endpoint rather than the household. That statement is scoped to cable and O2 does not extend it to the DSL and fibre lines on the same ASN, which is exactly why the number alone settles nothing. On mobile, a routable IPv4 is not what a line gets by default: it is a chargeable one-off that support enables before the subscriber changes the APN to netpublic and waits for a confirmation message. So one ASN covers an address shared by thousands of cable households and an address belonging to a single line, and only the block it came from tells you which.
Does O2 Germany use CGNAT?
On cable, permanently. An O2 moderator states that every o2 my Home connection running over a cable connection has DS-Lite active and that no switch to dual-stack is offered, so the IPv4 address a site records there is a shared tunnel endpoint rather than the household. On mobile a routable address is a paid option rather than the default, which is why the APN has to be changed to get one.
How do you get a public IP address on O2 Germany?
On mobile it is a chargeable one-off option. O2 support enables it on the line, the subscriber then sets the APN to netpublic and waits for the confirmation message, and the address arrives from O2 pools such as 46.114.0.0/15. On a cable connection O2 says it is not offered at all, at any price.
Is AS6805 the same network as AS13184?
Both are registered to Telefonica Germany, AS13184 under the holder string HANSENET. They are not interchangeable now: RIPEstat reports AS13184 as announcing nothing, its announced flag reading false, so no live address sits behind it. AS6805 still carries a bidirectional exchange with 13184 in its own routing policy, which is where the old relationship survives.