Loading...
Loading...
Railway, a developer-focused cloud platform, suffered a major outage after Google Cloud blocked the company’s account, triggering widespread errors, login failures, and inaccessible dashboards. The incident, first reported May 19, left many customer applications and developer workflows disrupted as Railway lost access to upstream Google Cloud infrastructure. Railway has escalated the issue with Google and partially restored access while working to bring all workloads back online. The outage underscores the fragility of single-cloud dependencies and the operational risk developer platforms face when third-party account actions or automated bans affect critical infrastructure.
This outage highlights operational risks for tech teams that rely on single-cloud or single-provider dependencies for developer platforms. It shows how third-party account actions can cascade into widespread service disruptions affecting developer workflows and customer apps.
Dossier last updated: 2026-05-20 01:15:57
Railway experienced a major outage after Google Cloud Platform actions led to customer services being blocked; Railway says the incident is resolved and published a post-mortem. Users on Hacker News criticized Railway for vendor choices, questioned communication with Google, and reported lingering 502 errors requiring manual redeploys. Discussion centers on responsibility—Railway owns uptime for its customers despite third-party cloud causes—and whether Google’s terms or billing issues played a role. The outage highlights supply-chain risk for cloud-native startups, the need for clearer incident communication and tooling for automated recovery, and potential commercial or legal fallout between platform providers and cloud vendors.
The Register : Cloud provider Railway says Google Cloud temporarily suspended its account without cause; in 2024, GCP deleted the account of an Australian pension fund — PaaS platform Railway says Google temporarily suspended its account on Wednesday without cause, inducing a major outage.
Railway suffered an ~8-hour platform-wide outage from May 19–20, 2026 after Google Cloud incorrectly suspended Railway’s production GCP account, taking dashboard, API, control plane, databases and compute offline. Cached network routes expiring caused the disruption to cascade to Railway Metal and AWS-hosted workloads because edge proxies relied on a GCP-hosted control plane to populate routing tables; users saw 503 and later 404 errors. Railway engaged GCP support, recovered account access, restored disks and compute, and gradually drained queued deploys while GitHub rate limits and reset TOS acceptances caused secondary user disruptions. Railway says it accepts responsibility for architecture that allowed a single provider action to cause a full-platform outage and outlines remediation steps.
Google Cloud Auto-Banned Railway.app Account – Major Railway Outage
Railway, a cloud development platform, suffered a major outage after Google Cloud blocked its account, causing dashboard access, logins, and services to fail. Railway identified the issue on May 19 and escalated directly with Google Cloud; partial access to some Google Cloud–hosted infrastructure has been restored while teams work to bring all workloads back online. The company reported errors like “no healthy upstream” and “unconditional drop overload,” and said its dashboard, API, and control plane remain impacted with no ETA for full recovery. This matters because platform outages at cloud providers or third-party account actions can cascade to developer tooling, CI/CD pipelines, and production apps that depend on hosted platforms. Engineers and customers should monitor updates and prepare incident mitigation steps.
Railway reported a major outage after Google Cloud blocked its account, cutting access to upstream cloud infrastructure and causing dashboard failures, login errors, API interruptions and “no healthy upstream” errors. The company identified the cause May 19 and escalated directly with Google Cloud while regaining partial access to some workloads; the platform team is restoring remaining Google Cloud–hosted services and the control plane for the dashboard, API and internal network. Railway said it has no ETA for full recovery but is in direct contact with Google Cloud support. The incident highlights cloud provider risk for developer platforms and dependency on single-cloud access.
Railway experienced a major outage after Google Cloud blocked the company’s account, causing widespread errors — including “no healthy upstream,” “unconditional drop overload,” login failures, and dashboard inaccessibility. Railway first reported an edge network disruption on May 19 and later identified loss of access to its upstream cloud provider; by 22:43 UTC it named Google Cloud as the cause and said it had escalated the issue. The platform regained partial access to Google Cloud–hosted infrastructure and is working with Google support to restore the dashboard, API, and control plane with no ETA provided. The outage highlights dependencies of PaaS/platform vendors on cloud provider account controls and incident response coordination.
Railway is experiencing a major outage after Google Cloud blocked the company’s account, causing widespread errors ("no healthy upstream", "unconditional drop overload"), login failures, and dashboard inaccessibility. Railway first reported a broad service disruption on May 19 and later identified the root cause as loss of access to its upstream cloud provider; the team has escalated the issue with Google and regained partial access to Google Cloud–hosted infrastructure while working to restore all workloads. The outage affects developers and customer applications running on Railway’s platform, highlighting risks of single-cloud dependencies and third-party account actions for cloud-native developer platforms.
Google Cloud Auto-Banned Railway.app Account – Major Railway Outage