Every HTTP request being served from edgeRegion: "asia-southeast1-eqsg3a" when Cloudflare enabled.
futsy
HOBBYOP

24 days 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?

Solved

24 Replies

connorwinston
PRO

24 days ago

I am also having this issue


Railway
BOT

24 days 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!


Railway
BOT

24 days ago

🛠️ The ticket Asia routing issue for non-Asia traffic has been marked as backlog.


brody
EMPLOYEE

24 days ago

We are going to be looking into this!


Railway
BOT

24 days ago

🛠️ The ticket Asia routing issue for non-Asia traffic has been marked as triage.


rossbrandon
HOBBY

24 days 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`


connorwinston
PRO

24 days ago

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

1461217883483935000


kylekz
PRO

24 days ago

i've been having this issue for 2 months, is it just randomly happening to other cloudflare regions now?


futsy
HOBBYOP

24 days ago

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.


scxr
PRO

24 days ago

also have this exact issue (all services are set to us-east)

1461314072661328000


kylekz
PRO

24 days ago

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


kylekz
PRO

24 days ago

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


scxr
PRO

24 days ago

im on about 815ms without caching rules 😭


kylekz
PRO

24 days ago

yeah mine is pretty rough right now
proxy on vs proxy off

1461316057733140500
1461316058303430700


scxr
PRO

24 days ago

yeah about the same


scxr
PRO

24 days ago

with vs without

1461317813728841700
1461317813988884500


steelzeh
PRO

24 days ago

How is this not a all-hands on deck from Railway? No updates for the last 7 hours?


futsy
HOBBYOP

24 days ago

Same here


macistador
PRO

23 days ago

We are also experiencing the same issue
x-railway-edge: railway/asia-southeast1-eqsg3a


scxr
PRO

23 days ago

any updates?


brody
EMPLOYEE

23 days ago

We have updated the routing configuration; it should be live globally soon.


scxr
PRO

23 days ago

seems to be working for me 👍

1461420147767247000


kylekz
PRO

23 days ago

huge, thank you

1461428714104422400


Status changed to Solved brody 23 days ago


Railway
BOT

23 days ago

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


Loading...