TRV-2026-1826Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1826 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-18T18:12:10.585272Z status: published lens: p_space sector: business headline: Microsoft pulls out of AI datacentre project in Essex over power supply concerns dek: The development of a huge AI datacentre hailed by the UK government has received a fresh setback after Microsoft pulled out of the project over concerns about power supplies. The development by the British company Nscale, heralded by ministers as the country’s largest AI datacentre when it was announced in 2025, was planned to open at Loughton in Essex next year. Doubts had already emerged about the scheme after the Guardian revealed in March that the location was still an operational scaffolding yard. Now there… gain_title: (none) problem_title: Electricity grid limits left Nscale's planned Loughton AI datacentre unable to get enough power until the early to mid-2030s, and Microsoft, its only publicly announced customer, withdrew. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: Electricity grid limits left Nscale's planned Loughton AI datacentre unable to get enough power until the early to mid-2030s, and Microsoft, its only publicly announced customer, withdrew. problem_evidence: it would not be able to supply enough power to the company’s Loughton datacentre until the early to mid-2030s | Nscale has lost its only publicly announced customer for the Essex datacentre quick_read: Microsoft has ended its agreement to anchor Nscale's Loughton datacentre in Essex, a site the UK government promoted in 2025 as its largest sovereign AI datacentre. The decision followed news that UK Power Networks could not supply enough electricity to the site until the early to mid-2030s. The episode shows how energy supply can limit AI infrastructure plans that governments and investors treat as engines of growth. It is still unclear whether Nscale can find onsite generation or a faster grid connection, and whether the setback will affect its planned New York listing. limitation: The article does not say whether Nscale can secure alternative power or a faster connection, and it leaves open whether the setback will delay Nscale's planned stock market flotation. tag: Evidence-backed problem key_points: Microsoft, expected to be the anchor tenant, told Nscale it was pulling out of its Loughton agreement. | UK Power Networks said it could not supply enough power to the site until the early to mid-2030s. | Nscale lost its only publicly announced customer for the Essex site but keeps Microsoft as a customer for a project in Norway. | Nscale says it is exploring onsite power generation and ways to speed up the grid connection. rundown: The Loughton project was announced by Nscale in 2025 and planned to open next year. It was highlighted in the government's AI strategy. The Guardian reported in March that the site was still an operational scaffolding yard, which had already raised doubts about the scheme. Nscale, backed by Nvidia, is described as a neocloud. The article says a growing number of voices see neoclouds as a vulnerability in the wider AI economy, as delays pile up and some companies take on risky debt. A delayed New York flotation could make these concerns more visible. Nscale says it remains committed to Loughton and the UK, is exploring alternative power sources and other UK sites, and describes its Microsoft relationship as strong. It attributes the problem to a London-wide grid issue that does not affect its other contracts. sources: - journalism | The Guardian | https://www.theguardian.com/uk-news/2026/oct/18/microsoft-drops-huge-ai-datacentre-project-in-essex-over-power-supply-concerns | 2026-10-18 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 3ff2c0126c59a6a7db4caab403ddf56ae45749a120262b3e7c8c2826a3e9c7ca
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1826 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace