TL;DR
Railway’s cloud-based services were disrupted after Google Cloud blocked their account. The company is working with Google to restore access, but some services remain affected. The incident highlights dependency risks on cloud providers.
Railway’s cloud infrastructure was disrupted after Google Cloud blocked their account, causing widespread outages in Railway’s dashboard, API, and internal services. The incident, confirmed by Railway, underscores the impact of cloud provider actions on dependent services.
On May 19, Railway reported a major service disruption affecting their platform, with errors including ‘no healthy upstream’ and login failures. By 22:43 UTC, Railway confirmed Google Cloud had blocked their account, making some services unavailable. Railway’s team escalated the issue directly with Google Cloud, which has since restored some access, but full recovery remains in progress.
As of May 20, Railway has regained some compute capacity on Google Cloud; however, ongoing network issues continue to prevent full service restoration. The company is working closely with Google Cloud support and exploring alternative options to bring services online. Some non-enterprise deployments are still paused, while enterprise services are unaffected.
Why It Matters
This incident highlights the risks of reliance on a single cloud provider for critical infrastructure. The disruption affected not only Railway’s platform but also serves as a reminder for organizations to diversify or strengthen their cloud strategies to mitigate such risks. The outage also raises questions about the stability and support responsiveness of major cloud providers.
cloud service outage recovery tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
Railway is a cloud-based platform that relies heavily on Google Cloud for hosting its services. The outage began on May 19, when Railway reported errors and service unavailability. Google Cloud’s blocking of Railway’s account was confirmed at 22:43 UTC, marking a significant escalation in the incident. Railway has been actively working to restore access and stabilize their infrastructure since then.
“We have access to some of our Google Cloud–hosted infrastructure and are working to restore the rest of the service.”
— Railway Platform Team
“We are in direct contact with Google Cloud support and working to resolve the ongoing networking issues.”
— Railway Support
enterprise cloud backup solutions
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It remains unclear when full service restoration will occur, as Google Cloud support is still working to resolve ongoing networking issues. The exact reasons for Google Cloud’s account blocking have not been disclosed publicly, and the potential for similar incidents in the future is unknown.
cloud infrastructure monitoring software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
Railway continues to work with Google Cloud support to resolve the networking issues and restore all affected services. The company has not provided a specific timeline but will issue further updates as progress is made. Monitoring the situation for any escalation or new developments will be key.
cloud service redundancy hardware
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What caused Google Cloud to block Railway’s account?
The specific reasons for Google Cloud’s account blocking have not been publicly disclosed. Railway is in contact with Google support to understand and resolve the issue.
When will Railway services be fully restored?
There is no confirmed ETA at this time. Railway is actively working with Google Cloud support to restore services and will update users as they have more information.
How does this affect Railway users?
Some users are experiencing outages or intermittent issues accessing Railway services, including dashboards and APIs. Enterprise users are less affected, but non-enterprise deployments remain paused.
Could this happen again?
The incident underscores vulnerabilities in cloud dependency, but it is not yet clear if similar incidents are likely to recur. Railway is exploring alternative solutions to mitigate future risks.
Source: Hacker News
