22 days ago
I have pushed the code to github and there is a new deployment. previously it used to happed instantly with in 5 min. Now it has been queued and not being deployed. Why?
2 Replies
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
We're sorry for the trouble. There's an active incident right now, "Deployments stuck in initializing", affecting deployments in all regions, and builds and deploys may be delayed or not progressing while we work on a fix. You can follow updates here, and we're still monitoring it.
When we checked your workspace, nothing was queued or in progress anymore. If your latest commit isn't live, you can push a new commit or use Deploy Latest Commit from the service's command menu (Cmd+K / Ctrl+K).
Status changed to Awaiting User Response brody • 22 days ago
brody
We're sorry for the trouble. There's an active incident right now, "Deployments stuck in initializing", affecting deployments in all regions, and builds and deploys may be delayed or not progressing while we work on a fix. You can follow updates [here](https://status.railway.com/incident/Z1JDWW1W), and we're still monitoring it. When we checked your workspace, nothing was queued or in progress anymore. If your latest commit isn't live, you can push a new commit or use Deploy Latest Commit from the service's command menu (Cmd+K / Ctrl+K).
22 days ago
Why is this a constant issue on delayed deployments? There was a security incident last week which was incredibly downplayed by Railway, and now a whole week later customers can't even restore websites? This is the most unreliable service I have seen in years.
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
15 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 15 days ago