How Deutsche Telekom Starves Its Own Customers

Why your 1 Gbps fiber line crawls at dial-up speeds during peak hours, and what the AS3320 peering war means for German internet users.

How Deutsche Telekom Starves Its Own Customers

Update (March 2026): The situation has not improved. Since this article was first published, several developments have confirmed that DTAG's peering practices remain a structural problem for German internet users. See the March 2026 Update at the bottom of this article.

Update (February 2026): There are indications that Cloudflare may be routing DTAG traffic through suboptimal paths, and that paid Cloudflare plans appear to get better routing than free tier domains. This is still under investigation. That said, packet loss within the Telekom network remains a widespread issue beyond just Cloudflare.

The operational practices of Autonomous System 3320 (AS3320), operated by Deutsche Telekom (DTAG), have long been a subject of technical and regulatory scrutiny. While most Tier 1 carriers utilize settlement-free peering to maintain global reachability, DTAG's restrictive interconnection policy is increasingly viewed by network engineers and digital rights advocates as a "terminating monopoly" strategy.

The Tier 1 Gatekeeper Logic

As a Tier 1 carrier, AS3320 does not purchase transit but relies exclusively on peering to reach the Default-Free Zone (DFZ). However, DTAG controls the "last mile" for approximately 15.2 million broadband customers in Germany, giving them a 40.3% market share in the fixed-line segment.

Because these users are only reachable via AS3320, DTAG enforces strict traffic ratio requirements. In the current internet ecosystem, where eyeball networks typically see significantly more inbound than outbound traffic, these requirements are difficult to meet for content providers without shifting to a paid peering model.

Strategic Congestion

Standard network engineering dictates that interconnection capacity should be expanded once a link reaches 70% peak utilization to prevent packet loss during bursts. Critics allege that DTAG does not expand capacity for partners who refuse to pay premium interconnection fees. According to Cloudflare, these fees are significantly above market transit rates, though it should be noted that Cloudflare is a direct party in this dispute and their figures reflect their own perspective.

This results in a predictable technical degradation for the end user:

Port Saturation. Links hit 100% capacity during evening peak hours.

Packet Loss and Jitter. Congestion leads to significant packet drops and increased latency. User reports on forums like the Telekom Community describe severe degradation during peak hours.

Routing Inefficiency. Traffic is sometimes routed through distant nodes (e.g., Stockholm or New York) to avoid saturated direct peering points in Frankfurt or Munich.

Cloudflare as a Focal Point

The impact is particularly visible for services utilizing Cloudflare. As Cloudflare serves as a CDN for a large portion of the modern web, bottlenecks at the AS3320 interconnection affect a wide range of services.

Professional Workflows. Developers report failed git clone commands from GitHub or extreme slowdowns when pulling images from Docker Hub.

AI and Productivity. Tools like OpenAI (ChatGPT), Canva, and Notion can time out or load incorrectly due to congestion at the AS3320 boundary.

Streaming. Twitch streams buffer, YouTube drops to low quality. These are the most commonly reported symptoms in user forums.

The VPN Diagnostic

The efficacy of using a VPN serves as strong evidence that the issue resides at the network boundary. By tunneling traffic, the data enters the AS3320 network via a different ingress point, typically one where the VPN's upstream provider has a higher capacity agreement with DTAG. The immediate restoration of nominal bandwidth via VPN confirms that the bottleneck is not the user's physical line, but a specific interconnection point.

That said, the VPN argument is not completely airtight. A VPN also changes the TCP connection characteristics (the VPN server terminates and re-initiates), can handle congestion control differently, and UDP tunneling may be less affected by packet loss than bare TCP. These factors could contribute to the observed improvement, though they are unlikely to fully explain the consistently dramatic difference users report.

Case Study: Deutsche Telekom vs. Meta

The peering dispute escalated into open legal warfare in 2024. Meta had been connected to Deutsche Telekom via dedicated interconnectors, paying approximately €5.8 million annually for this direct access. When the contract came up for renewal, Meta refused to renew but continued using the same infrastructure.

Deutsche Telekom sued, and in May 2024, the Regional Court of Cologne ruled in DTAG's favor, ordering Meta to pay a double-digit million sum (reportedly €20 million). Rather than comply, Meta announced the end of its peering relationship with Deutsche Telekom entirely, shifting to third-party transit providers.

Cloudflare's Position: Against Network Fees

Cloudflare has been vocal in opposing the "Fair Share" model that DTAG and other European telcos are pushing for. Their key arguments:

It favors large players. Only large corporations can afford premium peering fees. Smaller content providers and startups would be relegated to slower, congested transit routes.

Costs will be passed to consumers. Higher interconnection fees get passed down to end users through higher subscription costs for services.

Content providers already invest. Tech companies invest billions annually in network infrastructure (caches, CDN nodes) that reduce the load on ISP networks by delivering data closer to the edge.

It's not standard practice. Settlement-free peering is the overwhelming global norm because it benefits both parties.

Cloudflare maintains an open peering policy, peering with over 12,000 networks worldwide on a settlement-free basis. DTAG's policy is listed as "Restrictive" on PeeringDB.

Deutsche Telekom's Position: "Fair Share"

Deutsche Telekom frames the debate differently. In their June 2024 position paper to the European Commission, they argue:

Unsustainable traffic growth. With annual data growth rates of 25 to 50%, the current model where prices for data transport are marginal to zero is untenable. Traffic growth cannot be monetized despite increasing infrastructure costs.

Content providers should contribute. Large tech companies generate massive amounts of traffic without contributing to network maintenance and expansion costs.

Legal validation. The Cologne court ruling against Meta confirms that telecom operators can demand payment for a valuable data transport service.

Power imbalance. CEO Timotheus Höttges has characterized this as a question of whether the strongest players will dominate the internet or whether there will be a fair balance between all participants.

Deutsche Telekom argues that the time for regulation is now and has been pushing the EU to act on "Fair Share" legislation.

Regulatory Developments: 2025/2026

In April 2025, a coalition including epicenter.works, the Gesellschaft für Freiheitsrechte (GFF), and the vzbv filed a formal complaint with the Federal Network Agency (Bundesnetzagentur). They argue that DTAG's practices violate EU Net Neutrality (Regulation 2015/2120) by creating "paid fast lanes".

The EU's Digital Networks Act (DNA) 2026 has introduced a "voluntary conciliation mechanism." While presented as a way to resolve interconnection disputes, critics fear this could provide a framework for institutionalizing network fees, potentially weakening existing net neutrality safeguards.

A 2022 study by the Bundesnetzagentur concluded that imposing "fair contribution" fees could negatively impact consumers.

The Bottom Line

For IT professionals and corporate users, AS3320 represents an environment where connectivity quality is determined as much by commercial negotiation as by technical capacity. As long as this model persists, the "Netzbremse" (network brake) remains a structural reality of the German internet landscape.

Update: March 2026

Since the original publication, the peering situation in Germany has continued to deteriorate rather than improve.

The "Netzbremse" Persists

User reports throughout 2025 confirm that the core issue remains unresolved. Telekom customers continue to experience severe degradation during peak hours. Twitch streams buffer every few minutes, YouTube drops to 360p, and professional tools like GitHub and Docker become unusable. The diagnostic remains the same: a VPN instantly restores full speed, confirming the bottleneck is at the interconnection point, not the user's line.

Vodafone Follows the Playbook

In a concerning development, Vodafone has withdrawn from public internet exchanges in Germany. This mirrors the strategy that Deutsche Telekom has employed for years. If Germany's second largest ISP adopts the same approach, the "terminating monopoly" problem could extend well beyond AS3320.

BNetzA Complaint Still Pending

The formal complaint filed in April 2025 by epicenter.works, the GFF, and the vzbv against Deutsche Telekom for violating EU Net Neutrality regulations remains pending. The Bundesnetzagentur has not yet issued a ruling. Consumer advocates continue to mobilize, but regulatory action has been slow.

Meta Appeal Ongoing

Meta's appeal against the Cologne court ruling (the €20 million payment order) is still working its way through the legal system. The case is expected to reach the Düsseldorf Higher Regional Court and potentially the Federal Court of Justice, meaning a final resolution could take years. In the meantime, Meta continues to route German traffic through third-party transit providers rather than peer directly with DTAG.

EU Digital Networks Act: Concern

The EU's Digital Networks Act (DNA) 2026 introduced a "voluntary conciliation mechanism" for interconnection disputes. While framed as neutral arbitration, critics argue this could institutionalize network fees by giving dominant ISPs a formal process to demand payment for peering, effectively creating a regulatory framework for the very practices that net neutrality was designed to prevent.

Telekom's Response

It should be noted that Deutsche Telekom maintains a different view of the situation. In response to user complaints, the company has stated that they have no control over how external service providers route their traffic into the Telekom network. According to DTAG, sufficient capacity is available on their side, and temporary degradation occurs when external partners change their traffic routing. Telekom emphasizes that their networks operate reliably and that they are in constant dialogue with partners to ensure smooth data exchange across all network layers.

This is a fair point that adds nuance to the discussion. Peering is inherently a two-party relationship, and congestion at an interconnection point can be caused or exacerbated by either side. The question of who is responsible for upgrading capacity at a saturated link is precisely what makes this dispute so difficult to resolve.

However, the VPN diagnostic remains hard to reconcile with this position. If the Telekom network itself has sufficient capacity, it should not matter whether traffic arrives via a VPN tunnel or a direct peering link, yet the performance difference is consistently reproducible.

What Has Actually Changed?

Nothing fundamental. Deutsche Telekom's peering policy on PeeringDB remains listed as "Restrictive". The interconnection links that were congested in 2024 are still congested in 2026. The only difference is that the problem is now better documented and more people are aware of it.

For German internet users on DTAG infrastructure, the recommendation remains the same: if you need reliable access to international services during peak hours, a VPN or a different ISP is your only practical option.

Sources

Glossary

AS (Autonomous System). A network under a single administrative authority with its own routing policy. Every major ISP and content provider operates at least one. Deutsche Telekom operates AS3320.

BGP (Border Gateway Protocol). The routing protocol that determines how traffic flows between autonomous systems on the internet. It is essentially the GPS of the internet.

CDN (Content Delivery Network). A distributed network of servers that delivers content from locations physically close to the user. Cloudflare, Akamai, and Fastly are examples. CDNs reduce latency and load on origin servers.

Congestion. When more data is sent through a link than it can handle, causing delays, packet loss, and degraded performance. Similar to a traffic jam on a highway.

Default-Free Zone (DFZ). The set of routers on the internet that have a complete global routing table and do not need a "default route" to reach any destination. Tier 1 networks operate in the DFZ.

Eyeball Network. An ISP whose customers primarily consume content rather than host it. Deutsche Telekom is a classic eyeball network because its users download far more data than they upload.

Interconnection. The physical and logical link between two networks that allows them to exchange traffic. This can happen via peering or transit.

Jitter. Variation in packet arrival times. High jitter causes stuttering in video streams and poor voice call quality, even when average latency is acceptable.

Last Mile. The final leg of the network connection from the ISP to the customer's home. Whoever controls the last mile controls access to the end user.

Net Neutrality. The principle that ISPs must treat all internet traffic equally, regardless of its source, destination, or content. EU Regulation 2015/2120 enshrines this in European law.

Packet Loss. When data packets fail to reach their destination, typically caused by network congestion. Even 1 to 2% packet loss can noticeably degrade web browsing and streaming quality.

Peering. A direct connection between two networks to exchange traffic. Settlement-free peering means neither party pays the other. Paid peering means one party compensates the other for the connection.

PeeringDB. A public database where networks publish their peering policies and interconnection details. Policies range from "Open" (will peer with anyone) to "Restrictive" (strict requirements).

Port Saturation. When a physical network link reaches its maximum capacity. A saturated 100 Gbps port cannot carry more data without dropping packets.

TCP (Transmission Control Protocol). The protocol that ensures reliable data delivery on the internet. TCP retransmits lost packets, which means packet loss causes exponential slowdowns as the protocol backs off and retries.

Terminating Monopoly. When a network is the only path to reach a set of users. Since Telekom customers can only be reached via AS3320, content providers have no alternative route, giving DTAG leverage in peering negotiations.

Tier 1 Network. A network that can reach every destination on the internet through peering alone, without purchasing transit from anyone. There are roughly 15 to 20 Tier 1 networks globally.

Traffic Ratio. The ratio of inbound to outbound traffic on a peering link. Eyeball networks receive far more traffic than they send. ISPs sometimes require balanced ratios as a condition for settlement-free peering.

Transit. A paid service where one network carries another network's traffic to the rest of the internet. Unlike peering, transit is a commercial relationship with a clear customer and provider.

VPN (Virtual Private Network). A technology that encrypts and tunnels internet traffic through a third-party server. In the context of peering disputes, a VPN changes the network path traffic takes, often bypassing congested interconnection points.

Disclosure: Parts of this article are informed by my own experience as a Deutsche Telekom customer until February 2026. While I have aimed to present the technical and regulatory facts as objectively as possible, my perspective is shaped by having personally dealt with the peering issues described above.

Share this article