Skip to content
Volume still shows US West after service migration to EU West — how can I confirm backend region?
suf-sk
OP

a month ago

We are preparing our first production deployment on Railway and want to verify our persistent volume location before deploying.

Project: operaitions-me-production

Service: marketing-evolve-app

Service region:

EU West — Amsterdam

Volume mount:

/data

The volume was originally created while the service was in US West. The service was subsequently moved to EU West / Amsterdam, but the volume settings still display:

US West — California

Railway activity history confirms the service-region change, but we have not been able to establish whether the physical volume migration actually completed.

Current state:

  • production has never been deployed;
  • deployments: 0;
  • running instances: 0;
  • source disconnected;
  • volume usage displays 0 B;
  • no accepted production application database/data exists;
  • service configuration is EU West / Amsterdam;
  • volume UI still reports US West / California.

Could Railway confirm:

  1. Whether an attached volume should automatically migrate when the service region changes.
  2. How we can determine the actual backend/physical region of this volume.
  3. Whether the current volume is validly allocated for an EU West deployment.
  4. If it is still physically in the US, what the supported migration procedure is while retaining the existing volume.

We can provide the exact project, environment, service and volume IDs privately to Railway staff if needed.

Please do not delete, replace, detach or migrate the volume on our behalf without our explicit approval.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 2 months ago


sam-a
EMPLOYEE

a month ago

Your service is configured for EU West (Amsterdam), and the volume on /data is attached and healthy with essentially no data on it. Volumes follow their service's region, but the move happens as part of a deployment, not when the region setting is applied. Because this service has never been deployed, the volume is still in US West, and the US West label in the volume settings is accurate.

The region shown in the volume's settings is the one to go by. It changes only after a migration finishes, so it will read EU West once the volume has actually moved.

The volume is not broken. Its first deployment in EU West moves it to Amsterdam first, and then the service starts there. You don't need to detach or replace it, and there is nothing else to do beforehand. Larger volumes take longer to move and the service is down during the move, but at under 1 MB this one should migrate quickly. After that first deploy, check that the volume's settings show EU West. More detail is in our regions documentation.

We have not changed anything on the volume or the service.


Status changed to Awaiting User Response sam-a • about 2 months ago


Status changed to Solved suf-sk • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...