9 days ago
Service: Landing-Page-HAG-Partner
Project: hag-partner-landing
Deployments f32554a2-9214-44d4-8d1e-3b59bc1459b6 and 6afdcec7-b3bc-48f7-8b61-43984c983c46 both fail at the scheduling stage.
Error: /orchestrator.RegionService/ListRegions UNAVAILABLE: connect ECONNREFUSED 10.10.10.232:8775
The deployment never reaches build or deploy — it fails when Railway tries to assign the deployment to a region. Retrying did not help. The code is clean (only removed a migration file).
8 Replies
Status changed to Awaiting Railway Response Railway • 9 days ago
9 days ago
Those deploy failures were caused by a transient issue with an internal service that handles region assignment. It affected deploys platform-wide for a brief window and has since resolved. Your code was not the problem. Please try deploying again now, it should go through.
Status changed to Awaiting User Response Railway • 9 days ago
9 days ago
i did again 8 minutes ago, an is the same problem
Status changed to Awaiting Railway Response Railway • 9 days ago
Status changed to Awaiting User Response Railway • 9 days ago
9 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 9 days ago
8 days ago
no i still have the same problem
8 days ago
the error was in deploy logs Service: Landing-Page-HAG-Partner
Project: hag-partner-landing
Environment: production
Error en deployment:
/orchestrator.RegionService/ListRegions UNAVAILABLE: connect ECONNREFUSED 10.10.10.232:8775
El deployment falla en la etapa de scheduling (antes de build o deploy). Sucede en ambos intentos. Redeploy manual tampoco funciona.
Esto es un problema de infraestructura de Railway - no es del código ni de la configuración.
mayori
Please respond or edit your reply in English🙏
8 days ago
/orchestrator.RegionService/ListRegions UNAVAILABLE: connect ECONNREFUSED 10.10.10.232:8775