a month ago
Been trying to deploy a commit twice but keep seeing the following error:
This deployment failed due to a Railway infrastructure issue before the build or deploy stages could begin. Railway's internal region-scheduling service was unreachable, so no user code was ever executed. This is the second consecutive failure with the same error on this commit, making it a platform-side issue unrelated to your code changes.
I've re-deployed but still seeing this.
3 Replies
a month ago
Both of your recent deployments failed before any user code ran, and the deployment just prior to those succeeded normally. This was a transient issue, so please try deploying again now.
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
@Railway- deployments are failing....
Status changed to Awaiting Railway Response Railway • 30 days ago
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
This was part of a platform incident where deployments were slow to progress and could sit pending. For some deploys it also showed up as an "Unknown region" error.
It's now resolved and the deploy queue has fully cleared. Details here: https://status.railway.com/incident/US8W0QLQ
If your latest deployment still shows an old state, trigger a fresh redeploy and it should go through normally now. Apologies for the disruption.
Status changed to Solved Railway • 30 days ago