Railway incident

Deployments stuck

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

Update timeline

  1. resolved Mar 09, 2026, 10:16 PM UTC

    Type: Incident Duration: 1 hour and 22 minutes Affected Components: EU West (Metal / Amsterdam, Netherlands), US East (Metal / Virginia, USA), Southeast Asia (Metal / SIngapore), US West (Metal / California, USA), , Build Machines (Metal), Image Registry (Metal), , Builds (Railway Metal) → Deployments (Railway Metal) → Mar 9, 22:16:39 GMT+0 - Investigating - We are aware of an issue where new builds may appear stuck and fail to complete or progress slowly. Existing running services are not affected. We are actively investigating and working on a fix. Mar 9, 22:56:23 GMT+0 - Identified - We have identified the root cause and are deploying a fix. Mar 9, 22:26:24 GMT+0 - Investigating - Hobby, free and trial deploys have been temporarily disabled. We are continuing our investigation into the root issue Mar 9, 23:35:06 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 9, 23:38:27 GMT+0 - Resolved - This incident has been resolved. New deployments for free, trial and hobby have been re-enabled.

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