Improper routing of client -> edge -> service

I am based in the Netherlands
My service's location is also in the Netherlands
My service is proxied via Cloudflare

When I made a request, my request is sent to an edge server in Asia (issue is not always happening)

11 Replies

Project 146b3390-088d-483b-9c1b-9a7e3b2be785


Getting a http request id rq


Request id YO2Z_cNfS1WEhn_HacI7Nw
Commit fdf8f62
Branch/env prod


10 months ago

does the routing issue happen if you directly access the railway provided domain?


I'm using the Cloudflare proxied custom domain


10 months ago

I'm sorry but that doesn't quite answer my question


No, I am using a custom domain with Cloudflare proxy enabled
And not a domain generated by Railway


10 months ago

please try the domain generated by railway


maxeth
HOBBY

10 months ago

I noticed something similar for a railway service with region Amsterdam.

When requesting the public domain generated by railway directly from my browser (from EU west), i get railway/europe-west4, so all good.

But when I make an API request from certain cloud providers, like a Vercel serverless function or edge function hosted specifically in fra1 (Germany), I get railway/asia-southeast1-eqsg3a and the request time for the same route increases from ~200ms to ~1500-2000ms. I double-checked in Vercel's observability tab that it's actually requesting from fra1

I noticed that this occasionally lasts for multiple hours/days or something, then it eventually routes to railway/europe-west4 again as it should. 🤔


10 months ago

can you check again please?


maxeth
HOBBY

10 months ago

now it's railway/europe-west4-drams3a 👍


Loading...