Railway incident

Deployments may fail to go out

Minor Resolved View vendor source →
Started
Mar 09, 2026, 03:26 PM UTC
Resolved
Mar 09, 2026, 03:26 PM UTC
Duration
Detected by Pingoru
Mar 09, 2026, 03:26 PM UTC

Update timeline

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

    Type: Incident Duration: 1 hour and 7 minutes Affected Components: EU West (Metal / Amsterdam, Netherlands), US East (Metal / Virginia, USA), Southeast Asia (Metal / SIngapore), US West (Metal / California, USA), , Deployments (Railway Metal) → Mar 9, 15:26:35 GMT+0 - Investigating - We're investigating an issue causing a large portion of deployments to error, causing slowdowns across deployments and builds. Mar 9, 15:30:49 GMT+0 - Identified - We have identified the root cause of the issue and are working on a fix. Mar 9, 15:47:36 GMT+0 - Identified - 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. Mar 9, 16:04:43 GMT+0 - Identified - A fix has been pushed and is pending rollout. We're seeing issues with TCP proxy connections, related to this incident. Mar 9, 16:24:41 GMT+0 - Monitoring - We are seeing recovery for deployments. We are continuing to work on a fix for the TCP Proxy: Mar 9, 16:26:05 GMT+0 - Monitoring - We are seeing recovery, and have re-enabled Free, Trial and Hobby deploys. Mar 9, 16:33:18 GMT+0 - Resolved - This incident has been resolved.

Looking to track Railway downtime and outages?

Pingoru polls Railway's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Railway reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Railway alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Railway for free

5 free monitors · No credit card required