Google Cloud Suspends Railway.com Account Without Warning, Causes Major Outage
Key Takeaways
- ▸Google Cloud suspended Railway's account without advance notice or clear explanation, causing multi-hour outage affecting thousands of users
- ▸Despite spending $10M+ annually, Railway experienced slow support response (1-hour delay) and inadequate communication during the incident
- ▸Railway had previously experienced major disruptions from Google Cloud in 2024-2025 and had attempted to migrate away, but remained dependent on Google's infrastructure
Summary
Google Cloud temporarily suspended the account of Railway.com, a major PaaS platform customer, on May 19 without prior warning or explanation, triggering a widespread service disruption that lasted several hours. Railway's resources became invisible when the account was suspended, causing users to experience login failures, dashboard access issues, and deployment failures. The company, which spends over $10 million annually on Google Cloud, was left in the dark—Google's support team took an hour to engage, leaving customers irate and service recovery stalled.
Railway's solutions engineer expressed frustration about the lack of communication and slow response from Google, stating "Our contacts at Google were confused, customers are irate." The company has no clear explanation for why Google suspended the account, though they speculate it may have triggered an enforcement rule. Google has not publicly disclosed the cause of the suspension.
The incident is particularly damaging because Railway had previously attempted to reduce its Google Cloud dependency after similar incidents in 2024 and 2025. Despite migrating much of its infrastructure to colocation services, Railway maintained critical dependencies on Google Cloud for its control plane and databases. This latest disruption underscores the vulnerability of businesses dependent on cloud infrastructure, even when they've actively tried to reduce that dependency.
- Incident raises critical questions about cloud provider accountability, transparency in enforcement, and the business continuity risks of cloud dependency
Editorial Opinion
This incident exposes a troubling power imbalance in cloud infrastructure markets: major providers can unilaterally suspend accounts with minimal warning, potentially devastating dependent businesses with limited recourse. While cloud providers should have authority to enforce policies, the absence of advance notice, clear explanation, or prompt support response—particularly for high-value customers—fundamentally undermines trust and business confidence. Railway's situation also illustrates the illusion of security offered by multi-cloud strategies; even companies deliberately reducing Google dependency remain hostage to Google's enforcement policies for essential services.
