2 months ago
When I enable Cloudflare proxy, the edge region for every request in railway is being served from the asia-southeast1-eqsg3a edge region.
This is despite Cloudflare serving the request from many different data centers.
As a result, when the Cloudflare proxy is enabled, latency is unnecessarily high across all requests. Is anyone else having this issue?
24 Replies
2 months ago
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!
2 months ago
🛠️ The ticket Asia routing issue for non-Asia traffic has been marked as backlog.
2 months ago
We are going to be looking into this!
2 months ago
🛠️ The ticket Asia routing issue for non-Asia traffic has been marked as triage.
2 months ago
I am also experiencing this issue. Latency has drastically increased for my app and all requests are responding with header `x-railway-edgerailway/asia-southeast1-eqsg3a`
Can see the exact time here that the services first starting timing out and having issues, then when it started to get routed through southeast asia and normal baselien went from 100 ms to 2 seconds
i've been having this issue for 2 months, is it just randomly happening to other cloudflare regions now?
I'm looking back in my request history and it has been happening for a couple of weeks but that's all the history that I can go back. Something is very wrong between CF and Railway.
if you're using a cache rule to enable caching of API endpoints, you may want to disable that too as it increased latency massively for me: https://discord.com/channels/713503345364697088/1457873114321915904/1458700037851713558
i'd rather have it enabled but if the options are disabling cf proxy to bring latency down to expected values or keeping static assets cached, i'd rather keep static assets cached
2 months ago
How is this not a all-hands on deck from Railway? No updates for the last 7 hours?
2 months ago
We are also experiencing the same issue
x-railway-edge: railway/asia-southeast1-eqsg3a
2 months ago
We have updated the routing configuration; it should be live globally soon.
Status changed to Solved brody • about 2 months ago
2 months ago
✅ The ticket Asia routing issue for non-Asia traffic has been marked as completed.