18 days ago
I initiated a region change for my Postgres service from US East (iad) to Southeast Asia (asia-southeast1-eqsg3a) to co-locate it with my n8n Primary service.
Issue:
The first deployment succeeded and Postgres is running in the new region, but the volume migration is stuck on the MIGRATE_VOLUMES step.
Deployment details:
-
First deployment (SUCCESS): 9159c7fb-cd5a-47ea-b746-afc7d863a25d
- Postgres is running and operational in Southeast Asia
-
Second deployment (STUCK): 9580f9c4-adef-4e86-b804-f69975a18a1b
- Status: INITIALIZING
- Stuck on MIGRATE_VOLUMES step since 2026-08-03T15:49:43Z
- UI shows "Copying data from US East to Southeast Asia" but no progress
Project details:
- Project: angelic-mercy (4e8b2022-db31-4179-bd8f-3c9cfcc0613f)
- Environment: production (38563311-3e73-48ae-8ca0-4285bd79c5a0)
- Service: Postgres (5a5b4521-2f38-4eae-a2cd-864778349351)
Request:
Can the support team investigate and either:
- Unstick the volume migration, OR
- Force completion of the migration, OR
- Clarify if the old volume data in US East can be safely cleaned up
Postgres is currently operational with all data intact in the new region, so no data loss, but the stuck migration is blocking the full completion of the region change.
1 Replies
Status changed to Awaiting Railway Response Railway • 18 days ago
18 days ago
The migration completed at 16:21 UTC. It was not stuck, the cross-region copy was still running, and moving 4.3 GB from US East to Southeast Asia took about 31 minutes. That step does not report progress while it runs, so it looks identical to a stall.
The deployment you flagged as stuck is the one now live on the Southeast Asia volume. The earlier one was still attached to the old US East volume, so it was removed at cutover, which is expected.
Your data came across intact. Postgres was stopped gracefully at cutover and restarted without needing recovery, and it has been serving normally since.
There is nothing to clean up in US East. The old volume is deleted automatically after a migration, with the first attempt around 4 hours after cutover and a retry about 20 hours later.
Status changed to Awaiting User Response Railway • 18 days ago
11 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 • 11 days ago