Project: app-portal (id a4013529-26dd-486a-8c53-0b35589a1275)

Service: app-portal-backend (id e1de8956-9544-44cd-9b7f-ae0abc7bc813)

Environment: production

Region: us-west2 (service has a volume mounted at /data)

Every deployment of this service has been FAILING at the "Create container"

stage since 2026-06-09 ~01:24 UTC. Builds complete successfully; the container

is never scheduled and produces zero runtime logs. Your own deploy diagnosis

labels it an "Infrastructure Error — unable to schedule the container in

us-west2."

We have ruled out our side:

• Same code that deployed successfully on 2026-06-08 fails today (no code change

  between the last success and the first failure).

• 10+ consecutive failed deployments across multiple commits.

• Reducing the image from 2.75GB to 1.98GB made no difference (still fails at

  container creation in ~1 min).

• Other services in the same project/region (frontend, neo4j, telegram-gateway,

  backend-scheduler) deploy fine. Only this service (large container + /data

  volume pinned to us-west2) fails.

Sample failed deployment IDs:

9ab8f9c4-f172-4acf-afaa-4fa38e3b2192 (16:57 KST, slim image)

c300b6cf-9b4f-4b74-ad5b-9ee68b4c72d2

048d187e-b362-48f6-be64-b7160e522fd4

Please investigate node/volume scheduling capacity for this service in us-west2,

or advise whether we should migrate the service+volume to another region.