32 Government Services Go Dark: The Coding Flaw That Forced Britain Offline
Thirty-two UK government services are unavailable and four more are only partially working after ministers ordered a wave of precautionary shutdowns to contain a serious cybersecurity flaw in one of the internet's most widely used programming languages. Officials insist the country was not hacked — but the disruption shows how a single vulnerability in shared software can ripple across an entire nation.
What happened
Baroness Lloyd of Effra, the parliamentary under-secretary of state for the Department for Digital, Culture, Media and Sport, told the House of Lords on Thursday, October 22, that the outages "largely resulted" from precautionary measures taken to protect systems while security updates are applied.
The disruption stems from two serious vulnerabilities in PHP, the programming language that powers a huge share of the world's websites and online services. The flaws could allow attackers to run malicious code on affected servers without even needing login credentials — the kind of weakness that keeps cybersecurity officials awake at night.
"The government acted proactively ahead of public disclosure," Lloyd said, explaining that agencies had been alerted to the vulnerability and told to identify potentially affected systems, assess their exposure, and prepare to install security updates and mitigations before the flaw became public knowledge.
Downing Street sought to calm nerves, saying that "no large public-facing critical services are being affected" while acknowledging that some "limited services may temporarily be offline" as the security work continues. "This does not mean they were hacked," the prime minister's office added pointedly.
The 50,000-warning operation
The scale of the government's behind-the-scenes response is striking. Lloyd told peers that the National Cyber Security Centre — the UK's cyber-defence agency — had issued "50,000 proactive notifications to the wider economy to advise business and other organizations on what actions they should take."
The NCSC had first raised the alarm on October 21, urging organisations to check which of their systems run the affected versions of PHP and to establish their exposure. Its advice to any organisation unable to apply the security fixes immediately was blunt: "consider taking the system offline until it can be fully mitigated."
That guidance explains the 32 dark services: rather than risk leaving vulnerable systems exposed to attackers who by now know exactly where the flaw is, departments pulled them offline deliberately. It is the digital equivalent of evacuating a building before the fire starts.
But the private sector is feeling the pain too. Businesses across Britain are scrambling to audit their web infrastructure — and at least one prominent casualty has emerged: the Credit Protection Association reported that its own main website was disrupted by the PHP emergency, though its members' area stayed available.
Why PHP matters: the invisible engine of the web
To understand why a flaw in a programming language most people have never heard of can knock out government services, you need to know what PHP is. It is one of the foundational technologies of the modern web — the engine behind WordPress, which runs more than two-fifths of all websites, as well as e-commerce platforms like Magento and countless bespoke business and government systems built over the past two decades.
Because PHP is so ubiquitous, a critical vulnerability in it is not like a bug in one company's product — it is like discovering a structural weakness in a type of steel used in buildings worldwide. Every organisation running the affected versions becomes a potential target the moment the flaw is disclosed.
That is why the response went global within hours. Organisations around the world moved to secure potentially affected systems, and internet infrastructure giant Cloudflare reported on X that it had observed "millions" of hacking attempts across its network. There was, the company stressed, no evidence that any of those attempts had succeeded — but the volume shows how quickly attackers move to exploit a disclosed flaw.
What this means for businesses and households
For British businesses, the incident is a live stress test. The NCSC's 50,000 notifications went to companies of every size, and smaller firms without dedicated IT security teams face the hardest task: figuring out whether their websites, booking systems, or online shops run on vulnerable PHP — and finding someone who can patch them.
The timing compounds the pressure. With inflation running at 3.5% and economists anticipating another interest rate rise, businesses are already navigating fragile conditions; a forced website shutdown on top of that is the last thing any retailer or service provider needs heading into the busy end-of-year period.
For households, the immediate impact should be limited — Downing Street's assurance that no large public-facing critical services are affected means benefits payments, tax systems, and emergency services are expected to keep running. But anyone trying to use one of the 32 affected services will simply find it unavailable, with no published timetable for restoration beyond the government's promise to "restore the services safely and securely."
What happens next
The government says it "continues to monitor the situation closely and work with departments to maintain the security resilience and availability of public services." In practice, that means a race: patch and bring services back online before attackers find an unpatched system worth targeting.
Lloyd's statement that the government acted "proactively ahead of public disclosure" will be tested in the coming days. If the shutdowns hold and services return without a breach, ministers will claim vindication for the aggressive approach. If any system turns out to have been compromised before the shutters came down, the questions will be sharp — about why the flaw wasn't caught sooner, and whether 32 dark services was the price of safety or a sign of deeper fragility.
Either way, the episode is a reminder of an uncomfortable truth about the modern state: so much of what governments do now runs on the same shared, open-source software as everyone else's websites — and when that software breaks, the lights can go out in Whitehall just as fast as anywhere else.
Comments