Google Cloud Kills Railway Account, No Warning, No Explanation

Google Cloud suspended Railway's account via automated process with no prior warning, no human escalation path, and no public explanation. Railway published an incident report, and the HN thread asking whether Google should issue a public statement became a referendum on cloud provider risk. Multiple commenters said they were reconsidering GCP workloads entirely. One commenter noted Railway had already had a bad month in the press, and in both cases the damage came from automated decisions made by a third party.

The pattern here is a known and recurring problem: major cloud providers have automated abuse detection systems that can destroy a company's operations, and there is effectively no recourse for smaller customers. The GitHub breach via malicious VSCode extension ran in parallel, reinforcing that developer infrastructure is being attacked and mismanaged at multiple layers simultaneously.

Some commenters pushed back, noting that Railway agreed to Google's ToS and that expecting public statements about private customer incidents is unreasonable. But the operational fear is real regardless of who is technically right.