2 months ago
Since roughly 23:00 UTC on Aug 18 (2026), no deployment in my workspace can complete, across multiple projects. Two distinct symptoms:
- GitHub-triggered deployments never start.
Every push queues a deployment that sits indefinitely with the banner "Deployment queued due to upstream GitHub issues" — Initialization/Build/Deploy all "Not started". GitHub's status page has been fully green during this window, and the webhooks clearly arrive (the deployments are created), so the block appears to be on Railway's side.
- Project DB_API (20d229a4-5ed1-4c89-8f91-062aeda8ab31), service 2f72edd0-5f32-4b7a-bade-4cbe6ba5dae6, EU West: deployment 14ad35d9-0850-4353-aebc-05d2a260a809 QUEUED since 23:22 UTC; several earlier attempts from ~23:00 UTC onward were superseded while queued.
- Project DramWise_React (0e3f3b2c-80f8-4a4b-81a6-920de82bb8c4), service 95887784-d13d-41a6-9264-1b78a17fb2ec: same behavior at 23:04–23:05 UTC.
- CLI uploads bypass the queue but freeze at INITIALIZING.
To work around the GitHub queue I deployed both services from the CLI with railway up. Both uploads were accepted but have now been stuck in INITIALIZING for 30+ minutes (normally seconds):
- DB_API: deployment 31860500-c4ff-406b-9830-ac504242e0c1, created 23:25:30 UTC
- DramWise_React: deployment bc9af632-a9f2-4e5a-9733-ba5704b9efa2, created 23:28:02 UTC
Additional signal: the dashboard intermittently shows "Networking info temporarily unavailable — Domains and TCP proxy details could not be loaded."
The currently active (older) deployments keep serving fine — this is purely a build/deploy-pipeline blockage. status.railway.com showed all green when I checked.
What I've tried: waiting 30+ min, pushing fresh commits (new deployments queue with the same banner), and CLI railway up (stuck at INITIALIZING as above).
Request: please unstick or fail these deployments and advise whether this is a known incident. Happy to provide anything else needed.
4 Replies
2 months ago
We're sorry for the trouble. There is an active incident, "Deployments are slow to progress," affecting deployments across all regions including EU West, which is causing deployments to remain in an initializing state longer than expected. This lines up with both the queued GitHub deploys and the CLI deploys stuck at INITIALIZING that you're seeing. You can follow updates here: Deployments are slow to progress.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Looks like this happens after every github outage.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
We're sorry for the trouble. There is an active incident, "Deployments are slow to progress," affecting deployments across all regions including EU West, which is causing deployments to remain in an initializing state longer than expected. This lines up with both the queued GitHub deploys and the CLI deploys stuck at INITIALIZING that you're seeing. You can follow updates here: [Deployments are slow to progress](https://status.railway.com/incident/YYU63JUO).
2 months ago
When will the issue be solved? Any approximate date/time?
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We don't have an ETA to share, but the incident page is updated as progress is made and is the best place to watch for resolution.
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