Summary
- A Dutch environmental permit draft covers AM9/AM10 at Luttenbergweg in Amsterdam.
- Equinix is seeking an 80MW power envelope, but early delivery is constrained by grid congestion.
- The project shows how established European hubs can still attract demand while struggling to release power.
Equinix is moving forward with plans for two further Amsterdam data centres, although the project is being shaped by the electricity constraints now defining one of Europe’s most important digital infrastructure markets.
The Province of North Holland has published a draft environmental permit decision for the creation and operation of AM9/AM10 at Luttenbergweg 1 and 3A to 3D in Amsterdam. The notice also covers construction of the AM9 HT building as the first phase of the wider development.
The application is tied to Equinix Netherlands B.V. and carries case number 11481892. The draft decision was published on 6 July, with views invited until 17 August 2026, giving the project a live permitting window rather than a distant pipeline marker.
Power sets the build-out pace
The proposed campus has been reported as targeting an 80MW power envelope, a substantial addition in a market already under pressure from electricity demand, land constraints, and political scrutiny of large digital loads.
Initial delivery is expected to be limited by grid congestion, with early capacity restricted to only part of the permitted development. That phasing shows the gap between consented infrastructure and energised capacity. Planning permission, environmental permitting, and customer demand can all move ahead while the electricity system still determines when the asset becomes commercially usable.
Equinix’s existing Amsterdam estate gives the company a strong local base. Its own market page describes Amsterdam as a major digital gateway to Europe, with an established Equinix footprint across cloud, network, peering, and enterprise ecosystems. AM9 and AM10 would extend that position, but their delivery path shows how even incumbent operators must shape expansion around the power network.
Amsterdam remains strategically attractive because of its connectivity density, enterprise base, and role in European internet traffic. The city also sits within a Dutch data centre market that has faced more explicit scrutiny over energy use and land take than many newer European regions.
A mature hub under electrical strain
The planning and power profile of AM9/AM10 captures the balancing act facing mature hubs. Operators need more capacity for AI, cloud, interconnection, and enterprise workloads, while grid operators and public authorities are managing large-load demand alongside housing, transport electrification, industry, and heat decarbonisation.
That tension is changing how projects are financed and marketed. A phased campus can allow an operator to begin work and release some capacity, but it also affects customer commitments. Large users looking for contiguous blocks of power may struggle to treat a fully permitted campus as fully available if energisation stretches across several stages.
The Dutch permit notice also shows the growing weight of local environmental procedures. Data centres are being assessed as energy, cooling, building, and resilience assets, not just as commercial real estate. Their operating model must sit inside wider electricity planning, local environmental rules, and expectations around efficient use of scarce grid capacity.
For Amsterdam, the project is a test of whether a dense digital market can keep expanding without losing control of its utility constraints. Demand for data centre services remains strong, and Equinix’s platform gives the development a clear market rationale. The practical constraint is the power system’s ability to accommodate another major load while maintaining broader network priorities.
Europe’s largest hubs are likely to remain attractive, but their growth will become more staged, negotiated, and conditional. AM9 and AM10 show that capacity in mature markets can still be built, but not always on the clean development timetable implied by customer demand.
