2 months ago
Project: overflowing-rebirth (ID: 29500ab9-5ddd-4067-a270-86218b828628)
Service: activity-app (ID: 8767dcab-839d-4262-bd41-095dcdb11a86)
Environment: production (ID: 7e27bdaa-9349-417e-9543-f0c53118dc63)
Since ~01:50 (GMT+3) today, new deployments triggered by GitHub pushes have been stuck showing the message "Deployment queued due to upstream GitHub issues" and never progress past QUEUED/BUILDING. Affected deployment IDs:
6fe285aa-ea94-4b4d-90bd-9eeb954969b2 — stuck in BUILDING, zero build log output
125602fd-d273-4417-9459-a80179810e54 — stuck in QUEUED
ef1c5b99-a64d-4d52-8ceb-ba8475c37209 — stuck in QUEUED (triggered via a region scale to eu-west, as an attempt to force a different builder)
ba62563a-458b-4d94-ad6a-4b96e345e16f — triggered via railway up (bypassing GitHub entirely), also got stuck at "Taking a snapshot of the code..." — I removed this one manually.
Last successful deployment: a36d3cc5-0432-4e6d-b9b2-750768c243eb (SUCCESS at 01:46).
The dashboard itself shows a banner: "Deployments are slow to progress. We are investigating the incident." — so I understand this may be a known platform-side issue, but it's been over 2 hours with zero progress on any of my attempts (git push, region switch, and railway up).
Additional side-effect: because I tried scaling the service to eu-west to force a different builder, the service region is now stuck on EU West instead of its normal US West — I was unable to scale it back since no deployment has succeeded since. Could you help unstick the queue and confirm the region can be safely reverted to us-west2?
4 Replies
2 months ago
Apologies for the trouble. We're aware of an ongoing issue affecting deployments across all regions, which is what's causing your builds and queued deploys to not progress. You can follow live updates here: Deployments are slow to progress. Once deployments are flowing normally again, you'll be able to switch your service's region back to us-west2 from the service settings, as that change just needs a successful deploy to take effect.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
I can't progress on my project because of your mistake. When will this be resolved?
Status changed to Awaiting Railway Response Railway • about 2 months ago
Railway
Apologies for the trouble. We're aware of an ongoing issue affecting deployments across all regions, which is what's causing your builds and queued deploys to not progress. You can follow live updates here: [Deployments are slow to progress](https://status.railway.com/incident/YYU63JUO). Once deployments are flowing normally again, you'll be able to switch your service's region back to us-west2 from the service settings, as that change just needs a successful deploy to take effect.
2 months ago
I can't progress on my project because of your mistake. When will this be resolved?
2 months ago
We understand the urgency and apologize for the impact. We're not able to provide an exact resolution time, but the incident page is updated as progress is made and is the best place to watch for the all-clear.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago