Incident Report: May 19, 2026- GCP Account Suspension
Blog post from Railway
Railway experienced a significant platform-wide service disruption on May 19, 2026, due to an incorrect suspension of its Google Cloud production account, which affected all its GCP-hosted infrastructure, including its dashboard, API, and network components. The outage, lasting approximately eight hours, caused immediate errors and service disruptions for users, as cached network routes expired and the outage cascaded beyond GCP to impact all Railway workloads, including those hosted on Railway Metal and AWS. Recovery efforts involved restoring account access, persistent disks, compute instances, and networking, while also managing a backlog of queued deploys and addressing issues with GitHub rate-limiting Railway's integrations. In response, Railway is taking full responsibility and implementing architectural changes to prevent future occurrences, including removing dependencies on single upstream providers, enhancing its network's resilience by creating a true mesh infrastructure, and planning to limit Google Cloud services to secondary or failover roles, ensuring that its core services are not reliant on any single vendor.