Hello Railway team,

Our GitHub-backed Python/Django web service in EU West (ams) cannot deploy an update. The build succeeds and the build logs show the image export and image push completing, but deployment fails at "Deploy > Create container" before the application starts.

The error says the built image on production-dpams.railway-registry.com "could not be pulled from the registry" and suggests checking private registry credentials. This is an image built by Railway from our GitHub repository, rather than an image from a separately configured private registry.

This happened twice on October 28, 2026: the automatic deployment around 22:44 EDT, and one manual redeploy around 22:45 EDT using the same configuration. Both failed at the same step. The latest retry used Railpack 0.43.0 and Python 3.13.16; its build log shows the 176.3 MB image push completing.

Railway's built-in diagnosis reports "Infrastructure Error" and recommends contacting support if a redeploy fails again. Our previous deployment remains active and the live site responds, so the current impact is that we cannot release the update, rather than a complete outage.

Could you investigate whether the generated image is available to the runtime in ams and whether there is a registry authorization or replication problem? Please advise on a safe recovery that preserves the currently active deployment. The affected service is selected on this thread. I have both failed deployment IDs and can provide them through an appropriate private channel if needed.

Thank you,

Jefferson