I was just about to write up the same thing about the same issue, although in my case, I have selected US West (us-west2) region, and it's using railway/asia-southeast1-eqsg3a which is also causing latency issues.

Same here, 1s latency delay because of that (i'm in Brazil). What's happening?

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

I am also experiencing the same issue but with EU West (Amsterdam) location chosen. I am also proxying the traffic through Cloudflare and got latency issues ~1.2 seconds.

Just to know, i disable "proxy" feature in Cloudflare DNS and fixed the problem, but i'm now without proxy on Cloudflare.
If you guys need to fix the latency, until railway fix this, this is the way.

We have the same problem!

Disabling Cloudflare proxy did indeed help with latency, but for some reason it still uses the wrong region anyway. I have selected US West Metal and X-Railway-Edge comes back as US East Metal

✅ The ticket Asia routing issue for non-Asia traffic has been marked as completed.

This should be fixed now, can ya'll check again please.

For me it's fixed, i set the proxy on cloudflare and it's fine and working as it should. Thanks for the quick fix!

I'm still having some issues, but I'm not really sure if it should actually be this way, I still get the following regions depending on if I have Cloudflare Proxy enabled or disabled.

Selected Region:US West (for Preferred Deployment Region and (database, frontend, and backend services)

Without Cloudflare Proxy:railway/us-west2

With Cloudflare Proxy:railway/us-east4-eqdc4a

For me its fixed. In the morning I had a region displaying railway/us-east (thought it's due to Cloudflare proxy) but now I correctly receive eu-west.