a month ago
Three consecutive deployments failed at BUILD_IMAGE on October 9, 2026, between 21:02 and 21:09 UTC, before the application started. Two retries produced the same result. The previous successful deployment is still running.
Deployment IDs:
- debe06b5-932c-4666-959f-f29b8ffab6e2
- de81eccd-70b2-4d35-b121-5a89723607a4
- 9cf3b689-0a58-4583-8217-10d245145c56
Error: “Failed to build an image. Please check the build logs for more details.”
The latest build contains only this log entry:
2026-10-09T21:08:43.345342592Z info scheduling build on Metal builder "builder-chjaae"
There are no build-step error details or deploy logs. Railway’s automated diagnosis says the root cause is unknown and recommends contacting Railway so the team can inspect builder-side logs.
Could you investigate these failed builds and advise how to unblock deployment?
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
You're likely being affected by an ongoing incident, you can track here: https://status.railway.com/incident/O3D8H5MZ
a month ago
Sorry for the wait. These three builds failed because of a Docker Hub incident that blocked image pulls between about 21:00 and 22:00 UTC, before your build steps ran. That's why the log only showed the scheduling line. It's resolved now, so redeploying should go through. Let us know if it doesn't.
Status changed to Awaiting User Response Railway • about 1 month 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