a month ago
Hello,
I'm experiencing an issue with deployments that never complete - they remain stuck in the "Initializing" state indefinitely.
The dashboard/logs indicate that there is a problem in the Asia region. As a workaround, I tried to switch my server/deployment region to the Netherlands, but the region selection option is no longer available in the interface - it appears to have disappeared entirely.
Details:
- Issue: Deployments stuck in "Initializing" status, never complete
- Reported cause: Asia region outage/issue (as shown in the platform's status message)
- Attempted workaround: Switch deployment region to Netherlands
- Blocker: Region selection field/option is missing from the settings, so I cannot change the region myself
Could you please:
- Investigate why deployments are stuck in "Initializing"
- Restore the region selection option so I can manually switch to a different region (e.g. Netherlands)
- Provide an ETA for when this will be resolved
Project/Account: [add your project or account ID here]
Affected deployment ID(s): [add if available]
Timestamp(s) of failed attempts: [add if available]
Happy to provide screenshots or logs if needed.
Attachments
2 Replies
a month ago
Your service's current region (asia-southeast1-eqsg3a) has been marked invalid, which is why new deployments are stuck. The warning in your first screenshot says "Pick a replacement region below" - the region selector should appear directly beneath that warning in the Scale section of your service settings. Try scrolling down past the warning; your workspace's default region will already be pre-selected, and you just need to confirm it. Once you select a new region (e.g. EU West for Netherlands), your next deployment will go through.
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
This was part of a platform incident where deployments were slow to progress and could sit pending. For some deploys it also showed up as an "Unknown region" error.
It's now resolved and the deploy queue has fully cleared. Details here: https://status.railway.com/incident/US8W0QLQ
If your latest deployment still shows an old state, trigger a fresh redeploy and it should go through normally now. Apologies for the disruption.
23 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 • 23 days ago