Production has been down since 03:08 UTC on Oct 5 (502/503 on every route). Project modest-healing (a033fd4c-1c66-42db-9a54-bd17660a084f), environment production, service junk-ify-platform (fd27d617-e7f0-40f8-82c0-96577a638680), volume junk-ify-platform-volume (aea20fda-4eb8-4403-ad8a-7003d3c5f82c, /data, us-west2). Deployment bf279a74 got SIGTERM at 03:08 UTC and its teardown never finished; it still shows ACTIVE. Since then every deployment hangs at container creation: a0e1e64e and ada93af2 (cancelled), ca1b3f33 and 4d725a08 (FAILED, diagnosis 'Infrastructure Error, no code or config change needed'), 2059b6b9 (deploying now). The volume seems held by the old instance. Please release it and get the service running. Do NOT delete or wipe the volume: it holds our production database.