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.
Or..they couldn't remain compliant with one of the strictest cloud vendors' policies.
> Or..they couldn't remain compliant with one of the strictest cloud vendors' policies.
Which is it? They can comply or they can’t? Both sides can’t be true at the same time.
Being open minded is good but don’t keep it so open your brain leaks out.
If this was the case it would obviously be horrific. I did check to see, and I noticed that Railway is not listed as an ESP who sent any reports to NCMEC / CyberTipline in 2025, which seems like the wrong number for a hosting provider. Maybe they just have absurdly good customers.
https://www.missingkids.org/content/dam/missingkids/pdfs/202...
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:
So, I would actually like to know more (What did the account manager say exactly?) before I just simply jump onto the Google hate train because it's cool to do so.