Service: Otto.space (dad58334-d0ed-40d4-9107-872043cc9920)

Deployment: b2aca369-20fc-494f-b327-cd167c713f15

Environment: production

Every deployment attempt on July 17 fails immediately after container creation, before the build pipeline runs. No build logs, no SNAPSHOT_CODE, BUILD_IMAGE, or lifecycle steps beyond CREATE_CONTAINER. Deployments stop within ~30 seconds.

Evidence:

• Only CREATE_CONTAINER event in failed deployment, then "Stopping Container"
• Deployments created in FAILED/REMOVED duplicate pairs within 0.5 seconds
• Same repo built successfully on July 16 (still online)
• Config error: "Express deployment failed"
• This pattern persists across different commits
• Fresh redeploy from dashboard still failing with same pattern

The .railwayignore redeploy trigger was already fixed (PR #1 merged), so this appears to be a platform-side provisioning issue where containers are being stopped before the build pipeline executes.