25 days ago
Same incident as other June 12 sfo reports: build succeeds and the image publishes, but container creation/scheduling fails (~20s after image push). Multiple consecutive failures across different commits since June 12. Last successful deployment was June 9.
Service: copyreview-ai
Service ID: ee11d802-8777-44b7-9018-c8d6853eb196
Project ID: 0c34a234-aa2a-424a-bf78-3f9470c90b2c
Environment (production): b785dd6e-7a82-45c2-ba0b-299886f3bc9d
Region: sfo (US West). Single replica with a volume mounted at /data.
Railway's own diagnosis on the failed deploys: "Infrastructure Error — the container could not be scheduled. Build completed successfully and the image was published."
Example failed deployment ID: 2fd78dd2-5aad-4c2a-81f7-3b3f5745f81f
No infrastructure/config changes on our side; code changes are application-level only. Production is currently fully down (404). Please include this service in the sfo region remediation and let me know when the scheduler is restored. Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
24 days ago
Hey, you're right that this was the June 12 sfo issue, same incident the other reports are about. Container creation on a subset of US West hosts was failing, worst between 13:00-15:00 UTC.
It's resolved now. Trigger a redeploy and it should go through, your volume and data are unaffected. If it fails again at container scheduling, reply here and I'll check the specific host your volume lives on.
Status changed to Awaiting User Response Railway • 24 days ago
17 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 17 days ago