Cloud provider Railway says Google Cloud suspended its account without cause, resulting in an outage; in 2024, GCP deleted an Australian pension fund's account
The Register
Context & Ripple Effects
The reported Railway suspension follows earlier coverage of Google Cloud account-control failures: Google attributed UniSuper’s week-long 2024 outage to rare issues, and in 2018 said it would adjust automated fraud suspensions for customers with established payment histories.
That history matters because Google Cloud is simultaneously presenting strong growth and AI-compute demand as evidence that its infrastructure strategy is gaining traction; reliability of account governance is therefore part of the service proposition, not merely back-office operations.
First-order effects
Railway and its customers face an immediate availability risk when a GCP account suspension can interrupt the provider’s underlying infrastructure access.
Google Cloud must address another public allegation that account enforcement or recovery processes can produce outsized customer outages, alongside the earlier UniSuper incident.
Second-order effects
Cloud customers and managed-platform providers may put more weight on suspension safeguards, escalation paths, and recovery commitments when choosing or renewing infrastructure contracts.
AWS and Azure can use recurring GCP account-control incidents to emphasize operational support and continuity, particularly for customers that cannot tolerate a provider-level account lockout.
Third-order effects
If such incidents persist, cloud resilience discussions will broaden beyond regional failures and capacity to include the governance systems that can revoke access to otherwise functioning infrastructure.
The pattern could push larger customers toward multi-cloud designs or contractual controls around account suspension and restoration, though the available coverage does not establish how widely those changes will occur.
The trend: As cloud platforms become more central to customers’ operations and AI capacity demand rises, account-governance reliability is becoming a competitive dimension alongside compute scale and uptime.
It appears Google Cloud has blocked our account, and so some services are unavailable We've escalated this to Google and will keep people posted. Deepest apologies.
Google Cloud blocked cloud infra provider Railway's account, taking it offline. It's not the first time GCP did something unacceptable: in 2024, they deleted the infra of a $124B Australian fund. Not fully trusting GCP saved the fund's data. Full: https://blog.pragmaticengineer.c…
When you are on GCP, you NEED to have a backup on another cloud, because Google can delete everything. Unisuper did this, and avoided full data loss only thanks to this. I assume Railway will no longer rely on only GCP. They would be foolish to do so. https://newsletter.pragmatic…
This wild. Two years ago, Google deleted a large customer's account: Unisuper, an Australian retirement savings fund. It seems they now blocked an even larger customer, cloud provider Railway. This kind of story you never hear with AWS, Azure, or even Oracle. GCP 👎
Railway services have fully recovered. Some workloads may still need a redeploy, we're automatically redeploying any we detect as unhealthy. If your service isn't responding correctly, please trigger a redeploy from the dashboard or CLI. We're sorry for the disruption. A
Some thoughts on the discourse around @Railway team's outage. I was a mid-level SE at @datadoghq ANZ in 2023 when the company had a major, long lasting outage (actually started while I was mid demo). I was in a sales role, and what was most interesting to me was the response from
This is just unbelievable! Railway even has their own datacenters, but the APIs and edge network is on Google Cloud so everyone using Railway is down because Google just nuked their account 🤯
Google Cloud has blocked our account, making some Railway services unavailable. We have escalated this directly with Google. The Railway Platform team has since confirmed access to Google Cloud and is working on restoring access to all workloads. We have access to some of our
railway and every railway service going down because Google Coud blocked them was NOT on my bingo card I have heard horror stories of people getting blocked by google cloud and response/support being slow but this is wild, esp with the amount of spend they must be doing
I wonder how much damage this does to Google Cloud, let alone Railway. Has to be at least $1B for google long term. As someone who worked in gcp, I would describe the culture as the opposite of customer obsession. I have a few horror stories I'll keep to myself, but let's just
We have recovered our compute on Google Cloud, but services are unable to start because of ongoing networking issues on Google Cloud's side. We are engaged with Google Cloud support to resolve this and will post the next update as soon as we have more to share.
Does stuff like this ever happen with AWS? I only ever hear about it with GCP. It feels like they took the same technology they use to ban people's personal Gmail accounts and just pointed it directly at enterprise cloud customers running real businesses