9 months ago
Hello,
recently my service got promoted to the Metal Edge platform, shortly after that the response time has increased manifold, from around 50ms to upwards of 2000ms. I pinpointed railway to be the problem.
In the HTTP logs I noticed field edgeRegion:"asia-southeast1-eqsg3a", which was unusual, as my service is deployed in amsterdam, since thats the geographically closest location to me. After downgrading from Metal Edge to, not sure what the exact name, Google Cloud edge (?), the response time got back to normal and the field in HTTP logs is as expected edgeRegion:"europe-west4"
I must ask whether this an intentional change or why was my service auto-configured to route traffic through asia.
Thank you.
1 Replies
9 months ago
Hey Kobu,
This sounds like a routing issue. Can you give us some more diagnostic information?traceroute from the effected device to 66.33.22.11
traceroute from the effected device to 66.33.22.1
The x-railway-edge header from your http request
The deployment ID that is experiencing the issue
Status changed to Awaiting User Response Railway • 9 months ago
6 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 6 months ago