Summary

  • The ban lands on a named object: Article 29 forbids any switching charge from 12 January 2027 and, until then, caps charges at the provider's costs ‘directly linked to the switching process concerned’ — a direction to the provider, not a published number.
  • OVHcloud prints ‘Outgoing public traffic | Included’ in its Public Cloud price list and, two documents away, makes reversibility and content-recovery assistance ‘subject to a charge’ while stating that the service ‘does not include any restitution, recovery or migration of Content’.
  • The checkable line and the expensive line are different lines, because the definition can name egress and drafting can keep an unpriced service outside it.

The row sits in a block called Instance Public Traffic and it is two lines long. In the page as retrieved:

Summary
Name Price
Incoming public traffic Included
Outgoing public traffic Included

Beneath the table, one paragraph does the qualifying work: ‘Outbound public network traffic is included in the price of instances on all locations, except the Asia-Pacific region (Singapore, Sydney and Mumbai). In the tree regions, 1 TB/month of outbound public traffic is included for each Public Cloud project. Beyond this quota, each additional GB of traffic is charged.’ Note what the page prints and what it withholds. Both directions read Included; the paragraph then carves out three Asia-Pacific regions, allows a terabyte a month there, and says further gigabytes ‘are charged’ without printing a rate on the page as read. The page even carries its own typo — ‘the tree regions’ — which is what a working price list looks like rather than a legal exhibit (OVHcloud Public Cloud price list).

This is the line European law can see. Article 29 of Regulation (EU) 2023/2854, headed the gradual withdrawal of switching charges, is three sentences of clockwork: ‘From 12 January 2027, providers of data processing services shall not impose any switching charges on the customer for the switching process.’ Before that, ‘From 11 January 2024 to 12 January 2027, providers of data processing services may impose reduced switching charges on the customer for the switching process.’ And the cap: ‘The reduced switching charges referred to in paragraph 2 shall not exceed the costs incurred by the provider of data processing services that are directly linked to the switching process concerned’ (Article 29).

By my arithmetic, 12 January 2027 is 55 days after 18 November 2026 — twelve days left in November, thirty-one in December, twelve in January. Also by my arithmetic, the reduced-charge window runs three calendar years, from 11 January 2024 to one day past 11 January 2027. Neither figure is in the regulation; both are counts of its own dates.

What is genuinely absent from Article 29 is more interesting than what is in it. There is no ceiling figure, no formula, and no unit. The cap is a direction that a charge must not exceed costs of a stated kind, and the party who knows those costs is the party charging. There is also no register, no template and no filing duty in the article: the comparison instrument is left to a delegated act. Article 29(7) reads: ‘The Commission is empowered to adopt delegated acts in accordance with Article 45 to supplement this Regulation by establishing a monitoring mechanism for the Commission to monitor switching charges, imposed by providers of data processing services on the market to ensure that the withdrawal and reduction of switching charges, pursuant to paragraphs 1 and 2 of this Article are to be attained in accordance with the deadlines laid down in those paragraphs’ (Article 29(7)).

The definition names egress, and excludes two other things. Article 2, point (36): ‘“switching charges” means charges, other than standard service fees or early termination penalties, imposed by a provider of data processing services on a customer for the actions mandated by this Regulation for switching to the system of a different provider or to on-premises ICT infrastructure, including data egress charges’ (definition). Three elements carry the weight. The exclusions: standard service fees, early termination penalties. The trigger: actions mandated by this Regulation. The express inclusion: data egress charges. A metered transfer out of a cloud is exactly what the countdown is counting down to zero — and for a provider whose egress already reads Included, the ban's first target has arrived early, on paper, before the deadline.

Which leaves the drafting. A charge the provider does not characterise as a switching charge is outside the Article 29(3) cap, and outside the specification duty in Article 25, which requires the contract to state ‘switching charges, that may be imposed by providers of data processing services in accordance with Article 29’ (Article 25). Characterisation stops being an abstraction at that point and becomes the pricing constraint.

OVHcloud keeps one exit unpriced. Its General Terms of Services, clause 6.4, ‘Recovery of Content’, runs: ‘The Client is responsible for the recovery of Content. OVHcloud does not provide its clients with any specific means of recovering their Content, even prior to the expiration or termination of a Service. ... However, at the Client's request, OVHcloud may provide confidential technical information relating to the Service in order to facilitate Service reversibility and Content recovery operations. This assistance service is subject to a charge and to the signature of a specific confidentiality agreement. This service does not include any restitution, recovery or migration of Content’ (General Terms of Services, clause 6.4).

Read the last two sentences together and the structure appears. Assistance is available, subject to a charge, on request, behind a confidentiality agreement — and it is explicitly not the migration itself. No figure is printed. Whether that assistance is legally a switching charge, a standard service fee or something else is unresolved on the text read, and the clause's own carve-out may be there precisely to keep it in the excluded set. What is not unresolved is the documentary state: a customer can price the traffic row before signing and cannot price the assistance.

The map of the contract corpus shows the same shape. OVHcloud's contracts index, as retrieved, lists general terms, registry policies and product-specific conditions grouped by product. Nothing in that listing is titled after the Data Act, switching charges, egress or reversibility (contracts index). A document absent from a listing is not a document proven absent; the listing is what a reader has.

OVHcloud does not describe its own network the same way twice. A Public Cloud networking page states: ‘There are no additional charges on ingress and egress traffic, except for datacentres in Australia, India, and Singapore.’ It adds: ‘At OVHcloud, bandwidth is unlimited and unmetered. You can transfer as much data as you want at no extra cost. This applies to both ingress and egress traffic’ (networking page). The price list meters Singapore, Sydney and Mumbai and says the overage is charged. Two documents, two region lists, and ‘no extra cost’ against ‘are charged’. The price list is the one with rows; the marketing page is the one with adjectives.

What a customer does get, on the clock. Article 25 requires the switching clauses in a written contract available before signing; switching ‘without undue delay and in any event not after the mandatory maximum transitional period of 30 calendar days, to be initiated after the maximum notice period referred to in point (d), during which the service contract remains applicable’; a notice period ‘which shall not exceed two months’; and ‘a minimum data-retrieval period of at least 30 calendar days after the transitional period ends’. Where thirty days is technically unfeasible, the provider must notify within 14 working days of the request and indicate an alternative period not exceeding seven months. These are dates a buyer can hold someone to, and they are the part of the regime that does not depend on the provider's self-description.

The general application date is blunt: ‘It shall apply from 12 September 2025’ (Article 50). In the reproduction read, Article 50 carves out special dates for Article 3(1), Chapter III and Chapter IV and says nothing about Chapter VI, which places the switching chapter under the general date. The market rationale is stated in the recital the official page did serve: switching ‘without undue obstacles and data transfer costs is a key condition for a more competitive market’ (recital 78).

What was read, and what was not. The EUR-Lex HTML address returned its title block and recitals 78–80 as text; the ELI and CELEX text addresses returned no readable article body. Every article sentence quoted above comes from consistent reproductions of the Official Journal text, cross-checked across them, and from the official page for the recital. The clause 6.4 wording is an extract of the English general terms; the file retrieved for the UK edition gave its front matter and definitions, and which entity version governs a given customer is unresolved. No OVHcloud document read on 18 November 2026 cites Regulation (EU) 2023/2854, Article 29 or switching charges — a statement about ten documents, not about a corpus.

The bill for leaving a cloud will not vanish because a row says Included. It will be relocated to whichever document is not obliged to name a number — and that document is the one a customer accepts before knowing what it costs.