21 days ago
Details:
Two services experienced multiple deployment failures due to internal Railway infrastructure issues:
Affected Services:
planner-frontend (Service ID: 9d73f07b-932a-4b01-a3ed-c70efcf67f18)
planner-backend (Service ID: e484b67d-c1c6-43e9-bdc4-ac099801a705)Failed Deployments:
planner-frontend: 0ed3fea2-7524-4f40-9ae0-097f6066c305 (2026-05-18T06:25:06Z)
planner-backend: b3b9f729-718f-47f7-b27f-5b41f2b006a2 (2026-05-18T06:23:54Z)Error:
/orchestrator.RegionService/ListRegions UNAVAILABLE: No connection established.
Last error: connect ETIMEDOUT 10.10.10.42:8775
Issue: Multiple deployments failed in rapid succession (~2 minutes) before build/deploy stages could start. The internal orchestrator timed out connecting to the region service. Prior deployments succeeded with identical configuration.
Project: dependable-flexibility (ID: 63810bd2-c77e-4575-b5a8-dd3ae1d42a6e) Environment: production
1 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
20 days ago
These failures were caused by a platform incident affecting build infrastructure around that time. The incident has since been resolved and your deployments should go through normally now. Details here: https://status.railway.com/incident/4Q877DK9
Status changed to Awaiting User Response Railway • 20 days ago
Status changed to Solved nico • 20 days ago