8 hours ago
Railway Replica Region Mismatch After Migration
Hello Railway Community,
After migrating an isolated preview service
from US West to Amsterdam, the service
configuration shows one Amsterdam replica,
but Railway reports two running replicas.
Deployment status is SUCCESS, with
no critical issues.
We tested 18 HTTPS requests using
X-Railway-Debug.
All 18 reported:
X-Railway-Edge: cdg1
X-Railway-Upstream-Zone: railway/us-west2
This suggests traffic is still reaching
US West despite the Amsterdam configuration.
Could Railway help clarify:
-
How can we verify the actual region of
each running replica?
-
Could an obsolete US-West instance
remain after migration?
-
What is the safest way to reconcile
the replicas without affecting production?
-
Could the extra running replica
increase billed usage?
We have not authorized further restarts,
redeployments, or scaling changes.
Please request any internal project or
deployment identifiers through a private
channel if they are required.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 8 hours ago
8 hours ago
We confirmed one replica is running in Amsterdam and an obsolete replica is still running in US West. Sorry for the migration issue.
To reconcile them, select your isolated preview environment and choose Redeploy from the active deployment’s three-dot menu. This should replace both containers with one Amsterdam replica without changing production.
The extra replica can increase billed CPU and memory usage. We haven’t made any changes.
Status changed to Awaiting User Response Railway • about 8 hours ago