8 days ago
Hello Railway Support,
I need an explanation for a deployment state issue.
Project: englishai-backend (3639ef49-e807-4da7-8521-47fb436d09d4)
Environment: production (9aa201fa-8e40-410c-bf31-146f93f9703a)
Service: email-verifier (62de8870-b21e-4b23-a326-036416609486)
Region: us-east4-eqdc4a
CLI: railway 4.30.5
Current state:
- Latest deployment: 148846bf-b264-448c-b276-185d7d2c3320
- Created at: 2026-02-25T18:37:19.464Z
- Deployment status: DEPLOYING
- Service status: DEPLOYING
- Service stopped flag: true
Observed timeline:
- Previous deployment 61a434a4-4491-4c72-afa5-618cfbca68c8 reached SUCCESS.
- Newer deployments remain in DEPLOYING/queue-like states.
- We also saw queuedReason values such as “Waiting for deployment slot”.
Could you explain why the latest deployment remains in DEPLOYING with stopped=true and how to unblock/unstick this
service?
Thanks.
1 Replies
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
We're sorry for the trouble. We currently have an ongoing incident, "Builds and deployments are slow to progress," affecting deployments across multiple regions including US East. A fix has been released and we're working through the backlog of queued builds and deployments, which is why yours is stuck in DEPLOYING. Follow updates at https://status.railway.com/incident/cmm2cvzx50dxkx4rz5dx8efxh
Status changed to Awaiting User Response Railway • 8 days ago
a day 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 • 1 day ago