Hi Railway team, My Postgres service got stuck during the US West connectivity incident on Aug 10. Timeline: - Service was paused when my previous plan's credits ran out; I upgraded to a paid plan. - After upgrading, every redeploy in US West failed at "Deploy > Create container" — one with "Failed to start deployment" (~12 min), one with "An unknown error occurred" (~09:50). Deploy logs showed a repeated "Mounting volume on..." loop every ~30-60s. Diagnosis also failed. - I then attempted a region migration from US West to US East. The data copy failed with: "Failed to copy data from US West to US East — 0.00 B of 686.00 B — An error occurred during the data migration". The system auto-retried the migration backup 4 times (~10 min apart), all failed. - The service is now stuck showing "Initializing / Migrating volume..." for 40+ minutes. Service region shows US East but the volume is still in US West. Failed deployment IDs: a999682f, bc8b6a2b Project: lct-visuals-1.0 / environment: production Request: please unstick the migration (either complete it or revert the service back to US West). The volume contains production data and must be preserved — please do not reset it. Thanks!

Postgres stuck mid-migration (US West → US East) after connectivity incident — volume still in US West

ttknguyen

FREEOP

11 days ago

Hi Railway team,

My Postgres service got stuck during the US West connectivity incident on Aug 10.

Timeline:

Service was paused when my previous plan's credits ran out; I upgraded to a paid plan.
After upgrading, every redeploy in US West failed at "Deploy > Create container" — one with "Failed to start deployment" (~12 min), one with "An unknown error occurred" (~09:50). Deploy logs showed a repeated "Mounting volume on..." loop every ~30-60s. Diagnosis also failed.
I then attempted a region migration from US West to US East. The data copy failed with: "Failed to copy data from US West to US East — 0.00 B of 686.00 B — An error occurred during the data migration". The system auto-retried the migration backup 4 times (~10 min apart), all failed.
The service is now stuck showing "Initializing / Migrating volume..." for 40+ minutes. Service region shows US East but the volume is still in US West.

Failed deployment IDs: a999682f, bc8b6a2b

Project: lct-visuals-1.0 / environment: production

Request: please unstick the migration (either complete it or revert the service back to US West). The volume contains production data and must be preserved — please do not reset it.

Thanks!

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 11 days ago

milo

MODERATOR

11 days ago

Now that the incident is resolved; could you try migrate it again?

sam-a

EMPLOYEE

11 days ago

Good news: the migration finished successfully once the US West incident was resolved. Your volume is now in US East with all data intact, and your Postgres has been running normally since about 05:48 UTC on Aug 10. Your app deployed successfully right after it.

One important thing: your workspace doesn't have an active subscription right now, so new deploys may fail and your services could eventually be stopped. Paying an old invoice doesn't restart a subscription, you'd need to pick a plan again at railway.com/workspace/plans. Your volume data stays safe either way.

Status changed to Awaiting User Response Railway • 11 days ago

Railway

BOT

4 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 • 4 days ago

Welcome!