DownResolved 1
Google Cloud suspends Railway's production account and the whole platform goes dark for 8 hours
Railway says Google gave no notice before the suspension, and a control plane hosted there turned a one-cloud problem into a platform-wide outage.
At 22:20 UTC on May 19, Google Cloud placed Railway's production account in suspended status over activity flagged as a terms-of-service violation. Railway called it an incorrect automated action that extended to many accounts. Railway's dashboard, API and databases went offline, along with compute hosted on Google Cloud. Railway said Google had sent earlier violation notices but none before this suspension.1,2
Restoring account access did not restore services: disks, compute and networking each needed separate recovery. Railway's edge proxies relied on a Google-hosted control plane for routing, so once cached routes expired, workloads on Railway's own hardware and on AWS also returned 404 errors. GitHub then rate-limited Railway's login and webhook traffic during recovery.1,2
Railway put the impact at roughly eight hours, ending around 06:14 UTC on May 20, and said it takes full responsibility for the architecture that let one provider's action cascade. Google has not issued a public statement explaining why the account was suspended, according to InfoQ; Railway said it is working with Google on the process.1,2
Sources
- 1Incident Report: May 19, 2026- GCP Account Suspension
Railway · Official statement · May 20, 2026
- 2Google Cloud Suspends Railway's Production Account, Causing Eight-Hour Platform-Wide Outage
InfoQ · News report · May 30, 2026
- 3Google Cloud suspended major customer Railway.com without cause, causing outage
The Register · News report · May 20, 2026
Related
- Judged magnitude 4.0
- Judged magnitude 2.5
- Judged magnitude 4.0
- Judged magnitude 3.0