I'm experiencing deployment issues with my service in the production environment. Multiple deployments are stuck or queued: 1. **Deployment 0f83742a** (20:20 UTC) — Build completed successfully, but hung on CREATE\_CONTAINER step. Had to restart. 2. **Deployment ef9ad30d** (20:56 UTC) — Build completed successfully (image pushed at 21:02), but deployment status stuck on BUILDING step. Had to restart. 3. **Deployment aba88675** (21:08 UTC) — Currently QUEUED with no build events started. Has been queued for 15+ minutes. All three deployments are in the **us-east4-eqdc4a** region. The pattern suggests either a build queue backlog or resource constraints in that region.

Multiple deployments hanging/queued — possible platform issue in us-east4

the-bear-0618

PROOP

2 months ago

I'm experiencing deployment issues with my service in the production environment. Multiple deployments are stuck or queued:

Deployment 0f83742a (20:20 UTC) — Build completed successfully, but hung on CREATE_CONTAINER step. Had to restart.
Deployment ef9ad30d (20:56 UTC) — Build completed successfully (image pushed at 21:02), but deployment status stuck on BUILDING step. Had to restart.
Deployment aba88675 (21:08 UTC) — Currently QUEUED with no build events started. Has been queued for 15+ minutes.

All three deployments are in the us-east4-eqdc4a region. The pattern suggests either a build queue backlog or resource constraints in that region.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 2 months ago

chandrika

EMPLOYEE

2 months ago

Hi there, we just called on incident for this: https://railway.instatus.com/incidents/XLFH3W8Q

Seeing degraded build performance affecting queue times and the image registry. I'll keep updating the incident as we make progress.

Status changed to Awaiting User Response Railway • 2 months ago

chandrika

EMPLOYEE

2 months ago

The incident has been resolved

Status changed to Solved Railway • 2 months ago

Welcome!