Google cloud outage takes down banks
A Google Cloud outage briefly disrupted financial services, taking down neobanks like Revolut and prompting a broader discussion on the fragility of cloud reliance. The incident sparked debate on data sovereignty, the resilience of modern banking infrastructure, and the accuracy of outage reporting. Hacker News users weighed in on the real-world impact and the architectural choices that either protect or expose financial institutions to such failures.
The Lowdown
A recent Google Cloud outage caused significant disruption to several major financial institutions, including HSBC, Revolut, Bank of Scotland, Lloyds, and Equifax. While the full extent and duration of the impact were debated, the incident highlighted the critical dependencies modern financial services have on cloud infrastructure.
- Initial reports indicated widespread outages, with some users, like one Revolut customer, confirming complete loss of access to funds and services.
- Contrarily, some users banking with institutions like HSBC reported no issues, casting doubt on the reliability of user-generated outage trackers like Downdetector as definitive sources.
- The event reignited discussions about the resilience of neobanks, with Revolut facing criticism for its lack of customer access during the outage, while Monzo was praised for its robust 'stand-in' system designed for such scenarios.
- Commenters also delved into the concepts of 'compute sovereignty' and 'data sovereignty,' debating whether national cloud regions inherently provide better resilience or if they can paradoxically lead to single points of failure without proper multi-region redundancy.
This outage serves as a stark reminder of the cascading effects of cloud service disruptions on essential financial infrastructure, underscoring the ongoing challenge for banks to build truly resilient systems in an increasingly interconnected digital world.
The Gossip
Outage Reporting Ordeal
The discussion quickly turned to the veracity of the outage reports. While some users directly experienced severe disruptions (e.g., a Revolut user unable to access their main account or make payments), others reported their listed banks (like HSBC) were fully operational. This led to skepticism about the broad claims, with Downdetector being singled out as an unreliable source that often reflects user-reported issues rather than confirmed service downtime.
Neobank Nerves and Nimble Networks
The outage highlighted the varying resilience levels among neobanks. While Revolut users faced significant challenges with no access and no customer support, Monzo was lauded for its proactive disaster recovery strategy. Monzo reportedly uses a separate codebase and a different cloud provider for a 'stand-in' system, allowing limited but essential banking functionality during a main outage, prompting users to reconsider their choice of digital banking provider based on such architectural robustness.
Sovereignty Squabble: Compute vs. Redundancy
A deeper philosophical debate emerged around 'compute sovereignty' and 'data sovereignty'. Some commenters suggested that national requirements for data to reside within a country's borders might inadvertently lead companies to centralize in a single region, thus making them more vulnerable to regional cloud outages. Others countered that true sovereignty implies multiple data centers within a country, ensuring redundancy and not just geographic isolation, making it clear that sovereignty alone doesn't guarantee resilience without proper architectural planning.