The Digital Networks Act: Telecoms Rules That Reach Further Than Telecoms

The Digital Networks Act was introduced in January 2026 after several postponements, and most coverage filed it under telecoms regulation and moved on. That is a mistake for anyone building services that depend on connectivity economics, which is now almost everyone.

The Act rewrites the governance of European electronic communications. Three of its threads reach well beyond network operators: spectrum, security obligations, and the long-running fight about who pays for network capacity.

What it replaces

European telecoms has been governed by the European Electronic Communications Code, a 2018 directive that member states transposed at different speeds and with different interpretations. The result is what the Commission describes, accurately, as a fragmented single market: 27 national regulators, 27 spectrum regimes, and operators whose scale is limited by borders that do not exist for their competitors.

The Digital Networks Act is the attempt to fix that, and it is part of the wider One Europe One Market roadmap that also contains the European Business Wallet and a cybersecurity package.

The main threads

Spectrum harmonisation

Spectrum is licensed nationally, on national timetables, at national prices. For a continent trying to deploy consistent mobile infrastructure this is a structural handicap. The Act pushes towards longer, more harmonised licence durations and more coordinated assignment.

Why it matters outside telecoms: consistent spectrum policy is a precondition for consistent coverage, and coverage assumptions underpin everything from IoT product design to logistics tracking to connected vehicle features. If you ship hardware that depends on cellular connectivity across multiple member states, the fragmentation is currently your problem too.

A genuine single market for electronic communications

The Act moves towards country-of-origin style regulation and reduced authorisation friction for operating across member states, with the intent of allowing consolidation and cross-border scale.

Why it matters: European telecoms is unusually fragmented compared to the US or China, and fragmentation has kept operator margins thin and investment lower than the Commission would like. Consolidation is the explicit goal. Whether that produces better networks or just fewer operators is the argument.

Network security requirements

Security obligations for network infrastructure, sitting alongside NIS2 rather than replacing it. Telecoms operators are already essential entities under NIS2, so this is additional sector-specific detail rather than a new regime.

Why it matters: if you sell into telecoms, expect the security questionnaire burden to increase again. The supply chain scrutiny pattern that NIS2 started continues here.

Cloud and connectivity convergence

One of the more interesting threads. Networks and cloud infrastructure have converged technically, with edge computing, network function virtualisation and operators offering compute at the edge. The regulatory framework has treated them as separate industries. The Act begins to address that.

Why it matters: it intersects directly with the Cloud and AI Development Act. Both are aimed at European infrastructure capacity from different directions.

The fair share argument

The most contested part, and the reason the proposal was delayed repeatedly.

Telecoms operators have argued for years that a small number of large content and application providers generate the majority of network traffic and should contribute to network costs. Content providers respond that they already pay for their own infrastructure and transit, that consumers already pay for access, and that a traffic-based levy is a tax on popular services that would ultimately reach consumers.

Underneath the commercial argument is a net neutrality question. Any mechanism that makes traffic origin determine cost creates an incentive to treat traffic differently by origin.

Why it matters: if a contribution mechanism lands, the economics of delivering high-bandwidth services in Europe change. Video, gaming, large software distribution, model inference at scale and anything else that moves serious volume would be affected, and the cost would not stay with the largest providers. It would reach CDN pricing, transit pricing and eventually anyone buying bandwidth.

This is the thread to watch. The rest of the Act is technical governance. This one changes prices.

What a non-telecoms company should actually do

Very little in the immediate term, and a few things worth thinking about.

If your product depends on cheap high-volume delivery, model the sensitivity. Not because a levy is certain, but because knowing what a meaningful increase in European egress or transit cost would do to your unit economics is worth an afternoon. Most teams have never calculated it.

If you ship connected hardware across borders, watch the spectrum thread. Harmonisation is good news for you. It removes a genuine per-market engineering and certification cost.

If you sell to telecoms operators, expect more security documentation. The same artefacts that serve NIS2 and the Cyber Resilience Act will serve this. Build the pack once.

If you operate at the edge or sell edge compute, the convergence thread is your file. The regulatory boundary between network operator and cloud provider is being redrawn and that determines which obligations attach to you.

The honest assessment

The Digital Networks Act is a fight about market structure dressed as a technical modernisation. The Commission wants larger European telecoms operators investing more in networks. Operators want consolidation and a contribution mechanism. Content providers want neither. Consumer groups want net neutrality preserved. National regulators want to keep their powers.

Files with that many opposed interests do not move quickly, and this one has already been postponed several times before publication. Expect a long negotiation.

What is worth knowing now is the direction rather than the detail. European policy is consistently moving towards fewer, larger European infrastructure providers, more harmonised rules, and more scrutiny of dependency on non-European infrastructure. The Digital Networks Act, the Cloud and AI Development Act and the funding programmes described in our EU technology funding guide are all expressions of the same strategy.

Where this fits

The full legislative queue is mapped in our EU digital law pipeline, and the rules that already apply to your website and products are in our 2026 EU digital compliance guide.

Getting help

We build and operate software systems and infrastructure for companies across Europe, including the connectivity-sensitive parts: content delivery, edge deployment, cost modelling and the monitoring that tells you where bandwidth spend actually goes.

If you want a view on what changing European network economics would do to a specific product, or you need the infrastructure and dependency map that most of these questions start from, write to office@c9group.dev. More on the AWS cost optimisation page and the EU market entry page.

We are engineers rather than regulatory advisers, and this is a proposal in early negotiation rather than settled law.