Infrastructure Proximity Advantages in Cloud Markets

Detailed Explanation With At Least 6 Case Laws

1. Introduction

Infrastructure proximity advantages in cloud markets refer to the competitive benefits obtained by a cloud provider from locating data centres, computing capacity, network nodes, caching infrastructure, internet exchanges, submarine-cable connections, edge facilities, and other technical infrastructure physically or logically close to customers and important sources of digital traffic.

In cloud computing, competition is therefore not determined only by the nominal price of virtual machines, storage, or software services. Physical and network topology can itself become a source of market power.

A provider with infrastructure closer to customers may offer:

• lower latency;
• faster data transfer;
• greater reliability;
• better application performance;
• reduced network congestion;
• lower transmission costs;
• superior disaster-recovery options;
• easier regulatory compliance concerning data location;
• better connectivity to telecommunications networks and Internet Exchange Points (IXPs); and
• stronger integration with enterprise customers and digital platforms.

From a competition-law perspective, proximity can become particularly important where replication of infrastructure is expensive, access to suitable locations is scarce, network effects reinforce incumbency, and customers face substantial switching costs.

2. Meaning of Infrastructure Proximity

Infrastructure proximity has several dimensions.

A. Geographic proximity

A cloud provider may operate a data centre physically close to the customer's location.

For example, a customer in Delhi may obtain better performance from infrastructure located in or near northern India than from a distant facility.

Geographic proximity can reduce:

• physical transmission distance;
• latency;
• dependence on long-haul networks;
• congestion exposure; and
• certain network-transmission costs.

B. Network proximity

Physical distance is not always decisive. A geographically distant data centre may have better connectivity than a nearby one.

Network proximity therefore concerns:

• number of network hops;
• peering relationships;
• transit arrangements;
• backbone connectivity;
• Internet Exchange Points;
• telecommunications interconnection; and
• routing efficiency.

Thus, network topology can matter more than kilometres.

C. Edge proximity

Cloud providers increasingly place computing resources closer to end users through edge facilities.

This is particularly important for:

• autonomous vehicles;
• gaming;
• financial trading;
• industrial robotics;
• augmented reality;
• real-time AI inference;
• smart cities; and
• telecommunications.

Where milliseconds materially affect performance, proximity may become a competitive parameter rather than merely a technical feature.

3. Why Proximity Can Become a Competition Issue

Infrastructure proximity becomes a competition-law concern when it creates an advantage that rivals cannot reasonably reproduce.

The basic chain can be represented as:

Scarce location → infrastructure investment → lower latency/better connectivity → superior service → customer concentration → economies of scale → stronger market position → greater difficulty for rivals to enter.

This does not mean that every advantage resulting from a strategically located data centre constitutes unlawful conduct.

Competition law generally distinguishes between:

1. competition on the merits, and
2. strategic conduct designed to exclude or disadvantage competitors.

A provider is normally entitled to build efficient infrastructure. The concern arises when an incumbent uses control over infrastructure or access arrangements to foreclose competitors or exploit dependent customers.

4. Proximity as a Barrier to Entry

Cloud infrastructure requires substantial capital expenditure.

A new entrant may need:

• land;
• electricity;
• cooling systems;
• fibre connections;
• network interconnection;
• backup generation;
• physical security;
• regulatory approvals;
• specialised personnel; and
• customer connectivity.

A rival cannot necessarily reproduce the incumbent's infrastructure simply by purchasing additional servers.

This produces an important distinction:

Cloud capacity may be technologically replicable, while strategically located cloud infrastructure may not be economically replicable.

A competitor might therefore have sufficient computing capacity but still offer inferior service because its infrastructure is poorly positioned.

5. Economies of Density

Proximity advantages can generate economies of density.

Once a provider establishes a major data centre or cloud region, additional customers can be served from the same infrastructure.

The provider can spread fixed costs over a larger customer base.

This can produce:

more customers → more utilisation → lower average cost → lower prices/better investment → more customers.

Consequently, a geographically established provider may develop a self-reinforcing advantage.

6. Latency and Quality Competition

Traditional competition analysis often focuses heavily on price.

Cloud markets require a broader conception of competitive quality.

Latency can affect:

• transaction execution;
• video streaming;
• AI inference;
• gaming;
• industrial control;
• telecommunications;
• financial services; and
• real-time analytics.

Suppose Cloud Provider A offers 10-millisecond latency while Provider B offers 60 milliseconds.

For ordinary document storage, the difference may be irrelevant.

For high-frequency financial infrastructure or industrial robotics, it could be commercially decisive.

Thus:

Latency can function as a non-price competitive variable.

7. Data Sovereignty and Localisation

Proximity can also create regulatory advantages.

Some customers prefer or require data to remain within particular jurisdictions because of:

• privacy legislation;
• financial-sector regulation;
• government procurement requirements;
• national-security rules;
• sectoral localisation obligations; and
• contractual data-residency requirements.

A cloud provider with local infrastructure may therefore have access to customers who cannot easily use foreign infrastructure.

This can create a jurisdiction-specific competitive advantage.

However, competition authorities must distinguish genuine regulatory requirements from contractual or technical restrictions created by the incumbent itself.

8. Interconnection as a Proximity Advantage

A cloud provider may have an especially strong position where its infrastructure is located near:

• telecommunications carriers;
• IXPs;
• submarine cable landing stations;
• major enterprise networks;
• financial exchanges; and
• large content platforms.

The advantage is not simply "being nearby."

It is the ability to obtain high-quality network connectivity at scale.

This may create a network-access bottleneck.

A rival might construct an equally advanced data centre but still face inferior connectivity because the incumbent has already secured important interconnection arrangements.

9. Proximity and Switching Costs

Cloud customers often integrate applications deeply into a provider's infrastructure.

Once customers build systems around:

• proprietary APIs;
• databases;
• identity systems;
• networking;
• monitoring tools;
• AI services; and
• storage architecture,

moving to another provider becomes expensive.

If the incumbent also has superior geographic or network proximity, the customer may perceive switching as even less attractive.

This can produce:

proximity advantage + switching costs = stronger customer retention.

10. Cloud Regions as Strategic Infrastructure

Modern cloud providers frequently divide infrastructure into regions and availability zones.

A region may provide:

• local computing;
• local storage;
• redundancy;
• disaster recovery;
• low-latency access; and
• regulatory compliance.

Once a provider establishes a region in a commercially important location, competitors may need to spend enormous amounts to reproduce the same infrastructure.

The competitive question becomes:

Is the infrastructure advantage the result of legitimate investment, or has the incumbent engaged in conduct that prevents rivals from achieving comparable proximity?

11. Relevant Competition-Law Theories

Infrastructure proximity can implicate several doctrines.

A. Abuse of dominance

A dominant cloud provider may potentially infringe competition law if it uses control over infrastructure to exclude competitors.

B. Refusal to deal/access

If an essential or indispensable infrastructure facility is controlled by a dominant firm, denial of access may raise essential-facilities or refusal-to-supply concerns.

C. Discriminatory access

A provider could potentially discriminate between downstream competitors in access to infrastructure or interconnection.

D. Margin squeeze

Where an infrastructure owner competes downstream while supplying an essential input to rivals, pricing relationships can potentially produce a margin squeeze.

E. Exclusive arrangements

Long-term exclusive agreements for data-centre capacity, connectivity, power or strategically important locations can potentially foreclose rivals.

F. Bundling and tying

A dominant provider might potentially link cloud infrastructure access to other services, making competing cloud services less viable.

G. Merger control

Acquisitions involving data centres, network infrastructure, connectivity providers, cloud platforms or edge infrastructure can raise vertical and conglomerate concerns.

12. Case Law

The following cases are particularly useful for understanding the legal principles applicable to infrastructure proximity, essential infrastructure, network access, discrimination and technologically mediated market power.

Case 1: United Brands v Commission

Court of Justice of the European Union, 1978

Principle

The case is foundational for determining whether a firm possesses a dominant position and whether barriers prevent competitors from effectively constraining it.

The Court recognised that dominance concerns the ability of an undertaking to behave to an appreciable extent independently of competitors, customers and consumers.

Relevance to cloud infrastructure

In cloud markets, infrastructure proximity can contribute to this independence.

A provider controlling strategically located infrastructure may have:

• superior access to customers;
• lower latency;
• stronger network connectivity;
• greater economies of scale; and
• greater resistance to competitive pressure.

The case therefore supports analysing structural competitive advantages, rather than merely looking at market share.

13. Case 2: Commercial Solvents v Commission

CJEU, 1974

Principle

The Court established important principles concerning abusive refusal to supply where a dominant undertaking controls an input necessary for competitors operating in a downstream market.

Cloud relevance

Imagine a dominant infrastructure operator controls a critical physical or network input and subsequently competes with businesses that require that input.

If the infrastructure is indispensable and access is strategically denied, competition-law concerns can arise.

The analogy can apply to:

• data-centre interconnection;
• critical network infrastructure;
• cloud connectivity;
• specialised computing infrastructure; and
• infrastructure needed for downstream cloud services.

The case illustrates why vertical infrastructure control can create exclusionary risks.

14. Case 3: Bronner v Mediaprint

CJEU, 1998

Principle

Bronner is one of the leading European cases concerning refusal to provide access to infrastructure.

The Court adopted a demanding test for treating infrastructure as indispensable.

The fact that duplication is inconvenient or less economically attractive is generally insufficient.

Cloud relevance

This principle is extremely important for cloud infrastructure.

A competitor claiming that it needs access to an incumbent's:

• data centre;
• network;
• cloud region;
• edge facility; or
• interconnection infrastructure

would generally need to demonstrate more than simply showing that building its own infrastructure is expensive.

The question is whether duplication is economically or technically impossible or otherwise genuinely indispensable under the applicable doctrine.

Importance

Bronner prevents competition law from turning every competitive advantage into an access obligation.

15. Case 4: Oscar Bronner and the Essential-Facilities Boundary

The broader significance of Bronner is that competition law must balance two interests:

Infrastructure investment incentives

against

prevention of exclusionary bottlenecks.

If every successful infrastructure investment automatically generated an obligation to share, firms might have less incentive to build expensive infrastructure.

Conversely, if dominant infrastructure owners can indefinitely deny indispensable access, downstream competition can disappear.

Cloud markets present this tension particularly strongly.

16. Case 5: IMS Health v NDC Health

CJEU, 2004

Principle

The case concerned access to an intellectual-property-protected information structure and reinforced the exceptional circumstances under which refusal to license/access may constitute abuse.

The Court identified circumstances involving indispensability, elimination of competition and prevention of a new product for which consumer demand exists.

Cloud relevance

Cloud infrastructure increasingly involves combinations of:

• physical infrastructure;
• proprietary software;
• APIs;
• datasets;
• technical standards; and
• network architecture.

The IMS Health framework is useful when a dominant provider argues that competitors are requesting access to a proprietary technical ecosystem.

The competition authority must determine whether the requested infrastructure is genuinely indispensable and whether denial risks eliminating effective competition.

17. Case 6: Microsoft v Commission

General Court of the European Union, 2007

Principle

The Microsoft litigation is particularly significant for technology markets.

The case addressed refusal to provide interoperability information and the relationship between technological control and downstream competition.

Cloud relevance

Cloud infrastructure increasingly depends upon interoperability between:

• operating systems;
• cloud environments;
• databases;
• APIs;
• identity services;
• storage;
• cybersecurity systems; and
• enterprise software.

A provider can potentially strengthen its infrastructure advantage by making interoperability with competing clouds difficult.

Therefore, proximity plus interoperability restrictions can be more exclusionary than proximity alone.

18. Case 7: Magill

CJEU, 1991

Principle

Magill established important principles concerning exceptional circumstances in which refusal to provide access to protected information can constitute abuse.

Cloud relevance

The case is useful by analogy where a cloud provider controls information or technical resources that competitors require to offer viable downstream services.

For example:

• infrastructure information;
• technical interfaces;
• interoperability specifications;
• network access information; or
• essential operational data

could become competition-relevant where their absence prevents effective downstream competition.

The case demonstrates that control over information can amplify infrastructure power.

19. Case 8: Google Shopping

European Commission / General Court, 2017–2024

Principle

The Google Shopping litigation concerns the use of dominance in one digital environment to advantage the dominant firm's own downstream service.

The broader competition principle is that a platform may not necessarily escape Article 102 scrutiny merely because the conduct involves algorithmic or technologically integrated infrastructure.

Cloud relevance

Cloud ecosystems increasingly combine:

• infrastructure-as-a-service;
• platform services;
• AI models;
• advertising;
• cybersecurity;
• databases;
• developer tools; and
• application marketplaces.

A provider possessing superior infrastructure proximity could potentially favour its own downstream services through:

• preferential routing;
• better technical integration;
• priority access;
• latency advantages;
• capacity allocation; or
• preferential interoperability.

The case therefore helps explain how infrastructure advantages can interact with self-preferencing and leveraging theories.

20. Case 9: Deutsche Telekom v Commission

CJEU, 2010

Principle

The case is central to the law of margin squeeze in network industries.

It demonstrates how control over an upstream infrastructure input combined with downstream competition can create exclusionary effects.

Cloud relevance

The analogy to cloud markets is strong where a firm controls:

upstream infrastructure → network/connectivity → downstream cloud services.

For example, a vertically integrated infrastructure provider could potentially:

• charge rivals high access prices;
• provide its own downstream operation with favourable terms;
• maintain inadequate margins for competing downstream providers.

The competitive harm would therefore arise not necessarily from refusing access altogether but from economic conditions that make downstream competition unsustainable.

21. Case 10: Telefónica v Commission

CJEU, 2014

Principle

The case concerns broadband infrastructure and margin-squeeze analysis.

It illustrates the importance of assessing whether pricing and infrastructure arrangements can prevent an equally efficient competitor from competing effectively.

Cloud relevance

Cloud providers increasingly compete across integrated layers.

A provider may simultaneously operate:

• fibre infrastructure;
• data centres;
• edge computing;
• cloud computing;
• content delivery;
• enterprise networking.

This vertical integration makes Telefónica useful for assessing whether infrastructure ownership creates downstream foreclosure.

22. Infrastructure Proximity and Market Definition

A competition authority should avoid defining the market solely around generic "cloud computing."

Relevant markets might potentially be narrower according to:

• IaaS;
• PaaS;
• edge computing;
• specialised AI compute;
• GPU cloud services;
• enterprise cloud;
• public-sector cloud;
• low-latency cloud infrastructure;
• geographically constrained cloud services.

Geography can become especially important.

A cloud market may be:

• global for some services;
• regional for others;
• national for regulated workloads; or
• extremely local for latency-sensitive applications.

Therefore, geographic market definition must reflect the technical economics of the service.

23. Proximity and Essential-Facilities Doctrine

The essential-facilities question can be represented as:

Is the infrastructure indispensable?

↓

Can rivals reasonably duplicate it?

↓

Would denial eliminate effective competition?

↓

Can access be provided without undermining legitimate infrastructure investment?

↓

Is there an objective justification for denial?

If the answers strongly point toward indispensability and exclusion, competition-law intervention becomes more plausible.

24. Proximity and Data-Centre Scarcity

Physical infrastructure may become particularly scarce because of:

• limited electricity capacity;
• grid-connection queues;
• water availability;
• planning restrictions;
• land scarcity;
• fibre availability;
• environmental restrictions; and
• proximity to major connectivity hubs.

This is important because cloud competition can become constrained by infrastructure outside the traditional cloud market itself.

For example:

A cloud provider might possess no legally protected monopoly over computing technology but nevertheless enjoy significant market power because it controls scarce locations with electricity and connectivity.

25. AI Intensifies the Proximity Problem

AI workloads make infrastructure proximity increasingly important.

AI applications can require:

• GPU clusters;
• specialised accelerators;
• high-bandwidth networking;
• extremely low-latency interconnects;
• high-density power;
• specialised cooling;
• model-serving infrastructure.

Inference workloads are particularly sensitive to latency.

Therefore:

AI + cloud + edge infrastructure

may create new forms of infrastructure-based market power.

A provider controlling strategically positioned inference capacity could obtain an advantage over competitors whose computing resources are geographically distant.

26. Cloud Proximity and Network Effects

Proximity can interact with network effects.

A simplified model is:

More customers

→ more demand for local infrastructure

→ greater justification for additional capacity

→ better network interconnection

→ better service quality

→ more customers.

This creates a density feedback loop.

The incumbent's initial infrastructure investment can therefore become increasingly difficult for entrants to replicate.

27. Proximity and Customer Lock-In

A customer may initially choose a cloud provider because of proximity.

Later, the customer builds:

• databases;
• applications;
• AI pipelines;
• identity systems;
• security controls;
• monitoring systems;
• backups

around that provider.

The result is:

initial infrastructure advantage → migration costs → dependency → durable market power.

This means that competition authorities should examine not only present market shares but also future contestability.

28. Potential Anticompetitive Conduct

Infrastructure proximity itself is generally not unlawful.

Potentially problematic conduct may include:

1. Strategic exclusionary acquisition

Acquiring scarce data-centre locations primarily to prevent rivals from obtaining them.

2. Exclusive capacity agreements

Locking up scarce data-centre or network capacity through exclusivity.

3. Discriminatory interconnection

Giving the incumbent's services materially better network access than competing services.

4. Refusal of indispensable access

Denying infrastructure access where the legal requirements for an access obligation are satisfied.

5. Margin squeeze

Using upstream infrastructure pricing to make downstream competition commercially impossible.

6. Self-preferencing

Using superior infrastructure to favour the provider's own downstream services.

7. Bundling

Conditioning access to strategically important infrastructure on purchase of additional services.

29. Legitimate Business Justifications

A competition-law analysis must also consider legitimate reasons for infrastructure design.

A provider may legitimately prefer its own infrastructure because of:

• security;
• reliability;
• technical compatibility;
• capacity planning;
• disaster recovery;
• energy efficiency;
• cybersecurity;
• quality control; or
• legitimate investment incentives.

Therefore, proximity advantage ≠ abuse of dominance.

The critical question is whether the advantage results from competition on the merits or from exclusionary conduct.

30. Economic Assessment

Authorities should examine several variables:

31. Competition-Law Test

A useful analytical framework is:

Step 1 — Identify the infrastructure

What infrastructure produces the proximity advantage?

Step 2 — Identify the relevant geography

Is proximity important locally, nationally, regionally or globally?

Step 3 — Measure technical advantage

Assess:

• latency;
• reliability;
• routing;
• capacity;
• connectivity.

Step 4 — Assess replicability

Can competitors reasonably reproduce the infrastructure?

Step 5 — Examine customer dependency

Do customers have practical alternatives?

Step 6 — Examine conduct

Has the provider engaged in:

• exclusion;
• discrimination;
• tying;
• exclusive dealing;
• refusal to supply; or
• margin squeeze?

Step 7 — Assess foreclosure

Would the conduct materially weaken actual or potential competitors?

Step 8 — Consider efficiencies

Could the conduct produce legitimate technical or economic benefits?

32. Remedies

Where infrastructure proximity contributes to an infringement, potential remedies may include:

• access obligations;
• interoperability requirements;
• non-discrimination obligations;
• prohibition of exclusivity;
• structural remedies in exceptional circumstances;
• data portability;
• cloud switching requirements;
• transparency obligations;
• monitoring of interconnection;
• separation of infrastructure and downstream activities; and
• merger remedies.

However, forced access should generally be designed carefully because excessive regulation can undermine incentives to invest in new data-centre infrastructure.

33. Key Legal Insight From the Cases

The cases collectively demonstrate an important principle:

Competition law does not treat infrastructure merely as a physical asset; infrastructure can constitute a competitive bottleneck when control over it determines access to downstream markets.

Bronner establishes caution before imposing access obligations.

Commercial Solvents demonstrates the danger of using control over an upstream input to exclude downstream competitors.

Microsoft demonstrates how technological interoperability can become central to competition.

Deutsche Telekom and Telefónica show how vertically integrated infrastructure can produce exclusion through economic conditions rather than outright refusal.

Google Shopping demonstrates how technological advantages can be leveraged across related markets.

34. Conclusion

Infrastructure proximity is becoming an increasingly important determinant of competition in cloud markets.

Traditional cloud competition analysis tends to focus on:

• price;
• computing capacity;
• features; and
• software functionality.

But modern cloud markets require examination of the physical and network architecture underlying digital services.

Strategically located data centres, edge nodes, fibre connections, IXPs, electricity capacity and specialised AI infrastructure can generate substantial competitive advantages.

The central competition-law distinction is:

Efficient infrastructure investment
→ legitimate competition on the merits.

Control of indispensable infrastructure combined with exclusionary conduct
→ potential abuse of dominance/foreclosure.

The most significant future issue may therefore be whether cloud market power increasingly shifts from control of software and data to control of physical infrastructure, energy, connectivity, location and latency.

In that sense, infrastructure proximity can operate as a hidden structural barrier to cloud-market contestability, particularly when combined with network effects, switching costs, interoperability restrictions and vertical integration.