Railway provides automated code deployment by taking a GitHub repository and running the required setup in the cloud. Google temporarily suspended Railway’s account without stated cause, leading to a major outage. Railway’s status updates reported errors such as “no healthy upstream,” “unconditional drop overload,” login failures, and inability to access the dashboard. Railway noticed the issue around 22:00 UTC, and its resources appeared deleted or nonexistent. Google later explained the suspension, which made Railway’s resources invisible. Railway previously moved much infrastructure to colocation after earlier Google Cloud problems, but it still kept its control plane in Google Cloud and depended on databases running there. Railway reported slow engagement from Google support and speculated an enforcement rule may have been triggered.
"Railway automates code deployment by taking a GitHub repo and doing all the work needed to get it running from the cloud. It's struggled to do that for the last few hours and the company's status page tells the sad tale, starting with an update time-stamped May 19, 22:29 UTC that said the company is "investigating a widespread service disruption" that meant "Users may be experiencing errors including 'no healthy upstream', 'unconditional drop overload', login failures, and inability to access the dashboard.""
"Angelo Saraceno, a solutions engineer for Railway, told The Register the company noticed a problem at around 22:00 UTC. He said the company's resources appeared to have been deleted and appeared not to exist. Google has since explained it suspended the account, making Railway's resources invisible. "Our contacts at Google were confused, customers are irate," he added."
"Ironically, in 2024 Railway decided to shift much of its infrastructure into colocation services after Google "caused a multitude of problems that have posed an existential risk to our business." Those problems resurfaced in 2025 after more trouble at Google Cloud that again impacted Railway's services. But Railway kept its control plane in Google Cloud and still has a dependency on databases that run there. Those resources see it spend an eight-figure sum each year."
"Yet Saraceno said when this incident commenced, it took an hour for Google's support team to engage. "We are livid and still trying to get all the details," he said before advancing a theory that Railway somehow triggered an enforcement rule. Railway's status page says that as of 22:43 UTC the company "escalate"
Read at theregister
Unable to calculate read time
Collection
[
|
...
]