Hi Railway team,

The previous thread for this incident was accidentally marked as solved, but the production outage is still ongoing. This is a repost with additional evidence.

Our production service remains unavailable and returns HTTP 502.

Both a new image and a previously known-good production image fail at the CREATE_CONTAINER stage. The source snapshot, image build, and image publish stages complete successfully, but the container never starts and there are no application startup logs. Rolling back to the previously successful image produced the same result.

Additional evidence from the build logs:

• Railpack detects Node 22.23.2.
• npm install completes successfully.
• The application files are copied successfully.
• An OCI/Docker image is exported with a valid image digest.
• The image is pushed successfully.

Railway's deployment diagnostics also report:

“The build, image push and release all completed successfully, but the container never managed to start. The deployment stopped without recording any specific error.”

The deployment details show:

• Initialization: completed
• Build: completed
• Deploy: completed / 0:00
• Post-deploy: never started
• No application startup logs

The deployment event sequence confirms that SNAPSHOT_CODE, BUILD_IMAGE, and PUBLISH_IMAGE completed, while CREATE_CONTAINER never completed. The only deployment log recorded afterward is “Stopping Container”.

Because both the newly built image and a previously successful production image fail before the application process starts, this appears to be an infrastructure-level container provisioning or orchestration failure rather than an application boot failure.

Could Railway staff please inspect the internal CREATE_CONTAINER, compute scheduling, and volume attachment path for this service and help restore it?

Thank you.