a month ago
/orchestrator.RegionService/ListRegions UNAVAILABLE: No connection established. Last error: connect ECONNREFUSED 10.10.10.232:8775 (2026-07-22T20:49:21.828Z)
5 Replies
a month ago
Two deployments failed with that connection error around 20:44-20:49 UTC, but a subsequent deployment at 20:50 UTC succeeded and is currently running. If you encounter this again, redeploying should resolve it.
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
same here..and was about to do some midnight coding...
Status changed to Awaiting Railway Response Railway • 30 days ago
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
Not able to deploy
Status changed to Awaiting Railway Response Railway • 30 days ago
a month ago
The deploy failures from around 20:43-20:50 UTC were transient and have cleared. Deployments are succeeding again, so please try redeploying now.
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.
Status changed to Solved brody • 30 days ago