Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google resolves cloud outage affecting UK banks and websites

Revolut was one of the hardest hit, with banking services going down for many customers.

Google resolves cloud outage affecting UK banks and websites

A cloud service disruption affecting UK banks and websites was resolved by Google Cloud on Tuesday evening. The issue, caused by a power event at its London data centre complex, impacted multiple services at the europe-west2 region. Major UK services like Revolut, Lloyds Bank, and HSBC reported disruption on Tuesday morning. Google apologized for the inconvenience and thanked customers for their patience, promising to publish an analysis of the incident on its service health dashboard.

Cloud computing giants such as Amazon Web Services, Microsoft Azure, and Google Cloud provide services in local or regional sites called regions, containing their data centers. The HM Courts and Tribunals Service also experienced issues with their video platform for remote hearings. Many businesses, including small enterprises, faced significant financial consequences due to the outage.

Experts emphasize the reliance of economies on a few large cloud providers and the importance of quick service recovery and the availability of alternatives.

Written by urgent.news from BBC Business's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at bbc.co.uk →

More in Tech

Why my GETs worked but every POST got a 403: a CORS bug behind nginx in Docker

I'm a CS student building a tutoring management system: a Spring Boot REST API, a React frontend and PostgreSQL. While preparing the v1.2 release, I added a Docker Compose setup so anyone could run…

  • Student developed tutoring management system with Spring Boot, React, PostgreSQL.
  • CORS bug behind nginx in Docker caused 403 errors on POST/PATCH, not GET.
  • Fix used $httphost in nginx config to preserve port number and same-origin recognition.

How We Built an Atomic, Sharded Incremental Cache with 57ms Rebuild Times

When building a local-first repository intelligence engine, speed is everything. A cold build on a 100k-file benchmark can take 45 to 55 seconds.

  • TokenCap built atomic sharded incremental cache in src/incremental/cacheManager.js
  • Cache uses content-based SHA-256 checksums for integrity verification
  • Scoped invalidation enables 57ms rebuild time for single file edits

More from Tuesday 20 October →