In brief
- Google Cloud has marked the regional incident as resolved.
- The official duration was 7 hours and 52 minutes.
- Check your service's status: apps may recover at different times.
The incident is now resolved
Google Cloud listed the incident in europe-west2, its London region, as closed when we checked its European dashboard on October 20. The record gives a duration of 7 hours and 52 minutes and a final update at 07:05 PDT, or 08:05 in Mexico City. Affected products include AlloyDB, Apigee and BigQuery Data Transfer Service. This was not an outage affecting all Google products.
AP reported disruptions today at British banks including Lloyds, Halifax, HSBC and Revolut. By the time of that report, Lloyds said its app was working again. Each bank's status can change: this article covers the incident and its resolution, but does not confirm that every service is working again for every customer.
There is more to an app than its icon
To a user, an app is an icon. Behind the scenes, it may rely on sign-in services, databases and processing hosted by different providers. That is why tracing a failure means looking beyond the brand on the screen. A working home internet connection does not mean all those components are available.
The lesson is not that the cloud is useless or that local services never fail. It is that service continuity needs to be assessed from end to end. Restoring infrastructure and getting an app working again for its users are related, but they are not the same thing.
What to check before trying again
If you received no response after submitting a transaction, check its status through the official channel before trying again. An error message alone does not tell you whether a request was processed. It also does not establish that data was lost or that someone broke into the system.
Start with the service's own notices, then check its provider's status dashboard if you know which provider it uses. Do not give passwords or codes to accounts exploiting the confusion to offer support. The news today is that a specific incident has been resolved; the broader lesson is to distinguish confirmed information from rumor.
Sources and context
Sources used for this article. Follow the links to read the original material.
See the linked sources for more information. Corrections and contact →
