TL;DR
Railway experienced a major outage after Google Cloud blocked their account, affecting core services. The company is actively working with Google support to restore access, but no ETA is available.
Google Cloud has blocked Railway’s account, leading to a widespread outage of Railway’s cloud-based services, including dashboards, APIs, and internal infrastructure, with no estimated time for full recovery. Learn more about similar incidents.
Railway reported that on May 19, Google Cloud restricted their account, resulting in errors such as “no healthy upstream” and login failures affecting their platform. The company confirmed that access to some Google Cloud infrastructure was restored shortly after, but full service remained affected as of May 19 evening. See related Google storage policy updates.
By May 19, 23:37 UTC, Railway stated they were in direct contact with Google Cloud support and working to restore all workloads. Progress was made, with some workloads coming back online, but ongoing network issues on Google Cloud’s side continued to prevent full service restoration. As of May 20, 01:23 UTC, Railway confirmed they recovered their compute resources on Google Cloud, but services could not start due to network problems, and efforts to resolve this were ongoing.
Why It Matters
This incident highlights the dependency of cloud-based services on major providers like Google Cloud and the potential for widespread disruption when access is restricted. Railway’s outage affects developers and users relying on its platform for deployment and infrastructure management, illustrating the broader risks of cloud service outages.
cloud service outage monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
Railway is a cloud platform used by developers for deploying and managing applications. The incident began on May 19, when Google Cloud unexpectedly blocked Railway’s account, disrupting services. Railway has previously relied on Google Cloud infrastructure, and this is the latest in a series of incidents demonstrating the vulnerabilities of cloud dependencies. The company is actively working with Google to resolve the issue, which remains unresolved as of the latest update.
“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 network issues.”
— Railway support team
cloud infrastructure management software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is not yet clear why Google Cloud blocked Railway’s account or how long it will take to fully restore all services. The timeline for complete recovery remains uncertain, and the impact on users could persist until the issue is resolved.
As an affiliate, we earn on qualifying purchases.
What’s Next
Railway is continuing to work with Google Cloud support to resolve network issues and restore all workloads. Future updates will likely include progress reports on service restoration and any changes to the incident timeline.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why did Google Cloud block Railway’s account?
The specific reasons for Google Cloud’s action have not been publicly disclosed. The company is engaged with Google support to understand and resolve the issue.
How long will the outage last?
There is no estimated time for full recovery at this stage. Railway is working with Google Cloud support, but the timeline remains uncertain.
What services are affected?
The outage impacts Railway’s dashboard, API, internal network control plane, and other cloud-hosted workloads. Some services are gradually coming back online, but complete restoration is pending.
Will this affect other cloud providers?
Currently, the issue appears limited to Google Cloud. However, it underscores the risks of reliance on a single cloud provider for critical infrastructure.
Source: Hacker News
