Production service i12c (project 55e3e7de-5f38-427a-82c1-3606506fd43b, environment production, region us-east4) has been down for 6+ hours.

Symptom: every deployment builds and pushes the image successfully, then FAILS at "Deploy > Create container" with "Failed to create deployment." 40+ consecutive deployments. Deploy logs are empty - the container never starts.

Railway's own dashboard diagnosis says: "Railway's container scheduler was unable to create containers for this service across 40+ consecutive deployments spanning over 6 hours. This is not caused by any code or configuration change."

This is not a code/config change on our end - the same commit deployed fine earlier today. Note: a volume on this service was resized 500MB -> 2GB early in the incident; please confirm that is not blocking container creation.

Example failed deployment ID: f28c5fc9-f0fa-4b46-9733-160485a9f5ef

Our production site is down. Please escalate to unstick the container scheduler for this service.