API degradation causing slow or stuck deployments
Was Railway down? Railway reported “API degradation causing slow or stuck deployments” on Sep 29, 2026, 3:29 PM UTC. Full timeline below. This incident affects Railway — see live Railway status. Source: official vendor status feed.
Timeline
Sep 29, 2026, 7:15 PM UTC
The issue affecting our API and causing slow or stuck deployments has been resolved. A period of elevated load on our API caused a backlog to build in our deployment queue faster than it could drain. We applied several fixes to improve how our deployment system handles backpressure and temporarily paused new deployments for Hobby-tier projects while the queue recovered. All deployments have since resumed and are processing normally. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Sep 29, 2026, 6:37 PM UTC
We are seeing recovery and are monitoring this incident. Hobby deployments have been re-enabled.
Sep 29, 2026, 3:29 PM UTC
We are aware of an issue affecting our API that is causing slow or stuck deployments for some users. We are actively investigating and working to restore normal operations. We will provide updates as we learn more.
More Railway outages
- Dashboard loading issuesOct 5, 2026, 3:37 PM UTC · resolvedDegraded
- GitHub-triggered builds are delayedOct 5, 2026, 2:55 PM UTC · resolvedDegraded
- Slow attached storage for some users in US WestOct 4, 2026, 2:47 AM UTC · resolvedPartial outage
- Services and databases unavailable for some users in US WestOct 3, 2026, 4:55 PM UTC · resolvedPartial outage
- Potential intermittent connectivity issuesOct 2, 2026, 4:53 PM UTC · resolvedDegraded
- Slow dashboard and auth timeoutsSep 30, 2026, 3:06 PM UTC · resolvedDegraded