Railway outage exposes lingering GCP dependency despite bare-metal migration

Railway’s status page on May 19, 2026 shows a widespread degradation across nearly every customer-facing surface, with most services dropping to roughly 98.85% uptime for the month. The dashboard, Central Station, deployments, builds, private networking, observability, and even logins via GitHub and Google all took a simultaneous hit, while Railway’s own Metal edge network and storage buckets stayed clean. The pattern points to a single upstream failure cascading through anything still routed through Google Cloud.

The incident underscores how much of Railway’s control plane remains tied to GCP even after the company’s push toward its own Railway Metal infrastructure. Legacy GCP-hosted build machines, image registry, TCP proxy, and regional deployment zones all degraded together, and the auth path — which appears to depend on Google-side identity regardless of which provider a user picks — went down with them. Customers running purely on Metal compute were still exposed because logins, dashboards, and builds funneled through the affected GCP-backed components.

For a platform marketing itself as moving off hyperscalers, the event is a reminder that partial migrations leave the blast radius of the old provider intact. Until auth, the legacy build pipeline, and edge routing are fully cut over, a single GCP regional event can still take most of Railway offline.