This is just typical anti-Google FUD. Been on GCP for nearly a decade and as do my peers. Sure, you hear about a few stories like these and in this particular case with Railway, I would actually wait to see what caused the trigger for the suspension - both from Railway and from GCP. But, this sort of thing happens with every cloud provider including AWS (you can google for the same thing "AWS shut down our account with no warning") and you'll find tons of stories like these.
As a former GCP consultant, I can share that these sort of shut downs aren't random and it's usually due to the customer not being compliant - that breaks cloud compliance requirements for the big clouds, so automated systems flag it. Eg. Someone serving CP on their CDN, for instance.
The Railway incident report also doesn't directly address this at all other than:
May 19, 22:22 UTC - P0 ticket filed with Google Cloud. Railway's GCP account manager engaged directly.
> (What did the account manager say exactly?)
I doubt we'll ever know, especially if it makes Google look negligent (ie. not reaching out to the customer first before restricting their production account)
Whatever the account manager said didn't inspire confidence that this wouldn't happen again.
Finally, we are in planning to remove Google Cloud services from our data plane’s hot path, and keeping them only for secondary/failover.
> Whatever the account manager said didn't inspire confidence that this wouldn't happen again.
Or..they couldn't remain compliant with one of the strictest cloud vendors' policies.