We are investigating a widespread service disruption affecting Railway. Users may be experiencing errors including "no healthy upstream", "unconditional drop overload", login failures, and inability to access the dashboard. We are actively investigating and will provide updates as soon as possible.
We have identified the cause of the disruption. Access to our upstream cloud provider has been restored and we are working on a fix. The Railway dashboard and services running on our cloud infrastructure may continue to be affected until the fix is deployed.
Google Cloud has blocked our account, making some Railway services unavailable. We have escalated this directly with Google. The Railway Platform team has since confirmed access to Google Cloud and is working on restoring access to all workloads. We have access to some of our Google Cloud–hosted infrastructure and are working to restore the rest of the service. We apologize for the disruption.
We are working to restore the Google Cloud infrastructure that powers our dashboard, API, and internal network's control plane. We are in direct with Google Cloud's support team. We do not have an ETA at this time.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
