Production service stuck at CREATE_CONTAINER; prior-image recovery also fails
Anonymous
HOBBYOP

4 hours ago

An existing production service in region iad is unavailable (HTTP 502 on /_stcore/health). A deployment built successfully but did not complete container creation. A rollback and redeployment of the previously successful image also failed at CREATE_CONTAINER before health checks. Exact-ID build and deployment logs are empty; event error, reason, and detail fields are null.

Service ID: d81ff2f6-0a14-4a01-8f9a-45a2203e2bec

Failed rollback: 36641f98-8570-4f79-af7d-3c10c3d1ce65

2026-10-16 UTC: CREATE_CONTAINER started 16:19:20; FAILED at 16:35:17.

Prior-image recovery: 4f6a4087-e0dc-4ee3-a2bb-4f1e1f8194ab

2026-10-16 UTC: CREATE_CONTAINER started 16:35:20; FAILED at 16:51:19.

The existing volume reports READY in iad and remains attached at /data. No volume changes were made.

Could Railway investigate the backend container-creation failure, including provisioning or volume attachment, and advise a safe recovery preserving the existing volume? No further retries are running.

Awaiting Railway Response

0 Replies

Status changed to Awaiting Railway Response Railway • about 4 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...