Railway Up Timing Out
kausland23
PROOP

23 days ago

Service breakdown-engine (project ID 6f152e17-4433-4ec3-817c-af4b84cc64c6) cannot deploy via CLI. All railway up attempts since 22:18 UTC (about an hour ago) fail with backboard timeout, even after the Pro plan deploy incident was marked resolved an hour ago. Last successful deployment was at 15:49 UTC.

Error pattern: error sending request for url (https://backboard.railway.com/project/.../up?serviceId=8a0bd342-2934-4aa4-93fa-4fa0e00b8bbc) followed by operation timed out.

Already tried: CLI upgrade 4.33.0 → 4.44.0, railway unlink && railway link, multiple retries with and without --detach. Source configuration is CLI-based (no GitHub/Docker — has been that way for weeks across hundreds of successful deploys).

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 23 days ago


echohack
EMPLOYEE

17 days ago

Hey there!

I see that Railway Up finally worked for you. It looks like we had an incident affecting the deploy pipeline that might have contributed to the issue you were facing.


Status changed to Awaiting User Response Railway 17 days ago


Railway
BOT

10 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 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...