Hi,

We're evaluating how to run a production‑grade Postgres database (just using the standard PSQL image) on Railway, but I’m unsure how well it supports, or to what extent, workloads that need to scale across multiple regions within Railway.

If anyone has experience with this, it would be great to get insight on:

• How Railway handles cross‑region latency for read/write workloads

• Whether read replicas or multi‑region failover are supported (or any workarounds you’ve used)

• Recommended patterns for high availability, disaster recovery, and zero‑downtime migrations

• Any gotchas you encountered when scaling Postgres on Railway

• If you moved to Railway from a dedicated multi‑region provider (e.g., Neon, Crunchy, AlloyDB) and why?

My goal is to understand the realistic limits of Railway’s Postgres offering and what architecture people recommend when an app starts needing global performance and reliability.

Thanks in advance!