Railway incident

Suspected hardware failure affecting a subset of deployments in EU West

Minor Resolved View vendor source →

Railway experienced a minor incident on March 17, 2026, lasting 1h 42m. The incident has been resolved; the full update timeline is below.

Started
Mar 17, 2026, 10:57 AM UTC
Resolved
Mar 17, 2026, 12:40 PM UTC
Duration
1h 42m
Detected by Pingoru
Mar 17, 2026, 10:57 AM UTC

Update timeline

  1. investigating Mar 17, 2026, 10:57 AM UTC

    We are aware of an issue affecting a subset of services hosted in EU West. Some users may experience their services being unavailable or deployments failing to start. This is caused by a suspected hardware failure impacting a portion of our compute infrastructure in this region. We are actively working on recovery and services are beginning to come back online. Services with attached storage may take longer to fully recover..

  2. investigating Mar 17, 2026, 11:26 AM UTC

    We are currently investigating this incident. If your service does not have a volume attached, please try re-deploying it.

  3. identified Mar 17, 2026, 12:20 PM UTC

    We have identified the issue as a hardware failure on a single host in EU West. The affected infrastructure is being brought back online and workloads are recovering, some services have already been restored. Services with databases and attached storage may take a bit longer to fully come back. We will continue to provide updates as recovery progresses..

  4. monitoring Mar 17, 2026, 12:34 PM UTC

    All affected infrastructure is progressively recovering. If your service has not automatically recovered, please try redeploying. We are continuing to monitor..

  5. resolved Mar 17, 2026, 12:40 PM UTC

    This incident has been resolved..