2 months ago
Hi,
I have a service in Amsterdam (that connects privately to a database also in Amsterdam) and I am experiencing slow responses. I noticed that the "x-railway-edge" header is set to "railway/us-east4-eqdc4a". Also the traffic goes through Cloudflare Proxy.
Can it be linked to the slow responses ?
Thank you in advance
7 Replies
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
I also have this issue when Cloudflare Proxy enabled.
Service is Europe West, when accessing it through the up.railway domain it is served from that region.
When served through custom domain proxied on Cloudflare its served from railway/us-east4-eqdc4a.
Requests from Sweden, and proxied requests have very high latency
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Yes same thing happens for me as well, CF-RAY for me is from Copenhagen, goes to us-east4.
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!
brody
Hello,What region does the request originate from?
2 months ago
I have made a request from Paris in France
2 months ago
Hi - this should be resolved now. Let us know if you are still seeing any routing issues.
The Railway Team
a month ago
✅ The ticket Edge routing issue for non-US-East traffic has been marked as completed.