Hi Railway team,

I noticed a banner on my Postgres service (victorious-insight / Postgres / production) stating it was migrated from EU West to Southeast Asia. This migration was not requested or authorised by me.

What happened:

During yesterday's networking incident (Feb 19, 2026), my Postgres service crashed with a volume I/O error and was subsequently migrated to Southeast Asia. I deliberately chose EU West (Amsterdam) when setting up this service as it serves a UK-based business, and moving to Southeast Asia introduces significant latency for our users.

What I need:

I need the service migrated back to EU West (Amsterdam) without data loss. I have seen the revert warning which states it will restore from a backup taken Feb 20, 2026 at 11:30 AM - I want to understand if there is a way to do this without losing any data written after that snapshot, as the database has been active since then.

My concern:

Using the built-in revert option would take the service offline and restore from a point-in-time backup, potentially losing recent data. Is there a safe migration path back to EU West that preserves all current data?

Please advise on the safest approach.

Thanks,

Graeme