2 months ago
Production is fully unavailable because Railway routing has no active application for api.traqeer.com during incident VVL3A03V. Public requests return Railway fallback 404 Application not found without CORS headers, so the browser reports CORS and the product cannot use the API.
Healthy candidate deployment: d404daaf-344b-4e8e-b8b6-d9815ee5ac08. The process started successfully and its internal GET /health/deploy returns 200 repeatedly (confirmed at 2026-08-20T16:30:03Z). Deployment remains DEPLOYING and the public domain remains fallback 404. Rollback and redeploy both fail with: Deploys have been paused due to an upstream issue.
Please urgently force traffic restoration/cutover to the healthy candidate or restore the previous image outside the deployment pause. This is active full production downtime.
3 Replies
2 months ago
We're sorry for the trouble. There is an ongoing incident, "Deployments are slow; will be temporarily paused," affecting deployments across all regions due to a Google Cloud infrastructure issue. Your deployment being stuck in DEPLOYING and the "Deploys have been paused due to an upstream issue" message are direct symptoms of this. Once the incident is resolved, your deployment should complete and routing will restore. You can follow live updates here: status.railway.com/incident/VVL3A03V.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
This is not only a delayed deploy: the production domain currently has zero active backend route and every customer operation is unavailable. The candidate is healthy and has returned deployment health 200 continuously for more than 30 minutes. Please escalate to Railway on-call/ops for a manual traffic cutover or restoration of the previous image; waiting for the general queue leaves the application fully offline.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We confirmed your domain's DNS and certificate are valid, but the edge currently has no active deployment to route to because all 11 deployments in the workspace are stalled on their healthcheck step as part of the ongoing incident. Once the deployment pipeline resumes, the in-progress deployments will complete and routing will restore automatically. Manual traffic cutover is not an action available through this channel. You can follow the incident for live progress at status.railway.com/incident/VVL3A03V.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago