13 days ago
Hello Railway Support, We are currently experiencing an issue with deployments being permanently stuck in “Queued” status on our production service. Here is the context: Workspace plan: Hobby (recently upgraded today, February 25, 2026) Region: Railway Metal (EU West / Amsterdam) Repository: GitHub connected and receiving commits correctly Commits are detected by Railway However, deployments remain stuck in “Queued” and never start building We noticed there is an ongoing incident: “Builds and deployments are slow to progress” “Deployments (Railway Metal) – Degraded performance” “Builds paused for Free and Trial users” We upgraded from Free to Hobby specifically to avoid the build pause. However, even after upgrading, new commits continue to remain queued indefinitely. We have already: Pushed new commits after upgrading Disconnected and reconnected the GitHub repository Verified billing status (Hobby active) Confirmed the repository integration is functional Could you please confirm: Whether this behavior is still related to the ongoing Railway Metal incident? If deployments created during the outage window are permanently stuck? Whether we need to manually cancel/recreate the service to clear the queue? If there is any action required on our side to re-trigger builds properly? This service is production-critical for an active marketing campaign, so we would greatly appreciate clarification on expected resolution time or recommended workaround. Thank you in advance for your assistance.
Best regards,
Kevin
Workspace: successful-balance
Service: enigma-production-48e6
1 Replies
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
Apologies for the trouble. We're aware of an issue, "Builds and deployments are slow to progress," affecting EU West (Metal / Amsterdam) and other Metal regions. A fix has been released and we're currently working through the backlog of queued builds and deployments. Your queued deployments should begin processing automatically as the backlog clears, no action needed on your side. Follow updates at https://status.railway.com/incident/cmm2cvzx50dxkx4rz5dx8efxh
Status changed to Awaiting User Response Railway • 13 days ago
6 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 • 6 days ago