2 months ago
Hello, not sure if this is how it's intended to be when Cloudflare proxy is enabled, but initially it was routing my requests through Southeast Asia region but in a fix that was made it no longer does that; It now routes through US West when my selected region on railway is set to US West as my preferred region.
I have made sure that even my database, server, and frontend regions are set to US West. When disabling Cloudflare proxy it works, and I can see my requests are getting severed from US West, enabling the proxy again makes it serve through US East again adding some more latency.
6 Replies
2 months ago
Could you clarify where you're connecting from, and how are you determining where your requests are being served?
Status changed to Awaiting User Response Railway • about 2 months ago
ray-chen
Could you clarify where you're connecting from, and how are you determining where your requests are being served?
2 months ago
I am checking the network tab and looking at the response headers, specifically the x-railway-edge header, it's displaying railway/us-east4-eqdc4a. When I disable the Cloudflare Proxy, it shows railway/us-west2.
I am connecting from Baja California, Mexico, which is below California. I have US West selected, and I am not using multi regions since I am on Hobby plan, so I'm not sure why it should be using something else than what I have configured.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Can you try running this? Would like to see what it says.
https://cf-trace.up.railway.app/
Status changed to Awaiting User Response Railway • about 2 months ago
noahd
Can you try running this? Would like to see what it says.https://cf-trace.up.railway.app/
2 months ago
I tried running it, but what exactly am I supposed to look at?
Maybe this?Your local CF PoP: QRO
Status changed to Awaiting Railway Response Railway • about 2 months ago
abraham
I am checking the network tab and looking at the response headers, specifically the x-railway-edge header, it's displaying railway/us-east4-eqdc4a. When I disable the Cloudflare Proxy, it shows railway/us-west2.I am connecting from Baja California, Mexico, which is below California. I have US West selected, and I am not using multi regions since I am on Hobby plan, so I'm not sure why it should be using something else than what I have configured.
2 months ago
When I disable the Cloudflare Proxy, it shows railway/us-west2.
So our edge is correctly routing your request to the US West region (where you're connecting from) when you have Cloudflare disabled, and when you have Cloudflare enabled it is incorrectly routing your request to US East? That sounds like a Cloudflare routing issue
Status changed to Awaiting User Response Railway • about 2 months ago
ray-chen
When I disable the Cloudflare Proxy, it shows railway/us-west2.So our edge is correctly routing your request to the US West region (where you're connecting from) when you have Cloudflare disabled, and when you have Cloudflare enabled it is incorrectly routing your request to US East? That sounds like a Cloudflare routing issue
2 months ago
Hmmm yeah it's odd because there was a fix a couple of days ago where there were ISP problems and it was routing to South East Asia with proxy enabled and a fix was pushed, but it still kept showing the wrong region for me.
https://station.railway.com/questions/server-calls-are-taking-longer-than-usua-a054457c#sbs9
https://station.railway.com/questions/metal-edge-routing-us-east-traffic-throu-76f29e26#1ke7
I just checked again, and I think it somehow it got fixed on its own? It's now correctly showing my region, which is railway/us-west2.
I'll go ahead and mark this as solved I guess now, hopefully it doesn't happen again
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved abraham • about 2 months ago