Railway incident

Deployments may fail to go out

Resolved after 1 hour 6 minutes, affecting US East (Virginia, USA) (Deployments (US East)) and US West (California, USA) (Deployments (US West)) and 1 more, on March 9, 2026.

monitoring Mar 09, 2026, 04:26 PM UTC

We are seeing recovery, and have re-enabled Free, Trial and Hobby deploys.

Started
Mar 09, 2026, 03:26 PM UTC
Resolved
Mar 09, 2026, 04:33 PM UTC
Duration
1h 6m
Detected by Pingoru
Mar 09, 2026, 03:26 PM UTC

Affected components

US East (Virginia, USA) (Deployments (US East))US West (California, USA) (Deployments (US West))EU West (Amsterdam, Netherlands) (Deployments (EU West))Southeast Asia (Singapore) (Deployments (Southeast Asia))

Update timeline

  1. investigating Mar 09, 2026, 03:26 PM UTC

    We're investigating an issue causing a large portion of deployments to error, causing slowdowns across deployments and builds.

  2. identified Mar 09, 2026, 03:30 PM UTC

    We have identified the root cause of the issue and are working on a fix.

  3. identified Mar 09, 2026, 03:47 PM UTC

    We are continuing to work on a fix for this incident. New deploys for the hobby, free and trial plans have been paused until a fix is deployed.

  4. identified Mar 09, 2026, 04:04 PM UTC

    A fix has been pushed and is pending rollout. We're seeing issues with TCP proxy connections, related to this incident.

  5. monitoring Mar 09, 2026, 04:24 PM UTC

    We are seeing recovery for deployments. We are continuing to work on a fix for the TCP Proxy:

  6. monitoring Mar 09, 2026, 04:26 PM UTC

    We are seeing recovery, and have re-enabled Free, Trial and Hobby deploys.

  7. resolved Mar 09, 2026, 04:33 PM UTC

    This incident has been resolved.

Your product runs on more than Railway

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →