Your service is currently stuck in a DEPLOYING state due to a transient container creation failure on our side. We're aware of these infrastructure-side issues and are actively working on improvements. Please cancel any queued deployments and try a fresh redeploy shortly, as additional redeploys while the issue is active can compound the problem.

Followed your instructions — aborted the stuck deploy and waited until the service was back to "Online", then triggered one fresh redeploy. It also failed at "Deploy › Create container" after 1:01. App is still returning 502 with x-railway-fallback: true. Could you intervene at the platform level (e.g., release the stuck container slot or migrate the volume) so a new container can be created? Service: medstar-cold-email-db, project 5d74afd5-1e3e-428d-bb95-61847873c7c2.

Thanks — you've already done the right steps (cancelling the stuck deploy, single clean retry), so this isn't something more you can fix from your end. It's a known platform-side issue from today's US West networking disruption: the build/image succeed, but container creation fails because the service's volume is pinned to an affected host. That's why you're getting 502s with x-railway-fallback: true.

Your data volume is intact. This case needs platform-side recovery to release the stuck slot / migrate the service onto a healthy host — we're escalating it now with your project and service IDs (medstar-cold-email-db, project 5d74afd5-1e3e-428d-bb95-61847873c7c2). I don't have a firm ETA yet but will follow up here as it clears.