a month ago
You reached the start of the range
Apr 17, 2026, 11:43 AM
[Region: us-west1]
=========================
Using Detected Dockerfile
=========================
[...]
auth
sharing credentials for production-us-west2.railway-registry.com
0ms
importing to docker
5s
Build time: 33.45 seconds
=========================
Container failed to start
=========================
/orchestrator.RouterLegacyService/CreateDeployment DEADLINE_EXCEEDED: ctrd: failed to pull/unpack image: failed to resolve reference "production-us-west2.railway-registry.com/1c901c15-5602-4749-9567-a3614d0d039b:8ae26d17-0a24-4de3-acd3-5f62228a74fd": failed to do request: Head "https://production-us-west2.railway-registry.com/v2/1c901c15-5602-4749-9567-a3614d0d039b/manifests/8ae26d17-0a24-4de3-acd3-5f62228a74fd": dial tcp 162.220.232.124:443: i/o timeout
2 Replies
a month ago
Your build completed successfully but the deployment failed due to a transient platform-side networking issue when pulling the built image. Redeploying should resolve this.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Thanks for the report. What you're hitting is on our side, not yours. Your build and image push are completing fine, but our deploy nodes in us-west2 are intermittently failing to pull the image back out of the registry.
Your project is pinned to us-west2 because of the volumes attached to woodshed and Postgres, so region-switching isn't a clean workaround either.
We're actively working on it. Please hold off on retries for now, and I'll update this thread as soon as things are healthy again.
Sorry for the disruption.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved mirutanku • about 1 month ago