Railway incident
API degradation causing slow or stuck deployments
Resolved after 3 h 45 min.
- Started
- Ended
- Worst state
- Degraded
- On Railway’s status page
- Components
- API — backboard.railway.com, Deployments
Timeline
- Railway status page · Reported API degradation causing slow or stuck deployments
- Railway status page · Investigating 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.
- Railway status page · Monitoring We are seeing recovery and are monitoring this incident. Hobby deployments have been re-enabled.
- Railway status page · Resolved 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.
Cite this incident
Site Qwality, “API degradation causing slow or stuck deployments,” Sep 29, 2026, https://siteqwality.com/is-railway-down/incidents/railway-202609291529/
Free to quote with a link to this page.