16 days ago
Same issue — build succeeds, then fails pulling from production-us-west2.railway-registry.com at 162.220.232.124:443.
This is definitely a service-specific registry issue. The registry has pt-portal's service ID in a bad state. Since another service in us-west2 works fine, this isn't regional.
You need to contact Railway support immediately with:
Service ID:
c480ed43-ee58-4195-a7db-f5829e35f751Service name:
pt-portalIssue: Registry node
162.220.232.124cannot serve images for this service (consistent i/o timeout on manifest pull)Request: Clear service registry entry or migrate to healthy node
This requires backend intervention — I can't fix it from here. The registry has your service in a corrupted state.
3 Replies
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
We've confirmed the image pull timeouts on your deployments. We're not currently seeing widespread registry issues, so this is likely transient. Please retry your deployment.
Status changed to Awaiting User Response Railway • 16 days ago
brody
We've confirmed the image pull timeouts on your deployments. We're not currently seeing widespread registry issues, so this is likely transient. Please retry your deployment.
16 days ago
I have been retrying for over an hour
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
We understand this is frustrating. Unfortunately, since we're not seeing widespread reports of this issue from other users, this appears to be an isolated case. We don't have the capacity to investigate one-off reports at this time. Please continue retrying your deployment.
Status changed to Awaiting User Response Railway • 16 days ago
7 days 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 • 7 days ago