Edge routing going through Asia instead of Amsterdam (Increased latency)
tommyvahabov
PROOP

a month ago

Hi Railway Team,

I'm experiencing unexpected latency (~160-330ms) on my service that used to respond in 30-40ms. After investigation, I found the issue:

Configuration:

  • Service: QuizPilot (web app)

  • Service Region: Amsterdam (europe-west4)

  • Domain: quizpilot.uk (via Cloudflare)

Issue: Looking at response headers, I see:

cf-ray: ...LHR

 (user is in London)

x-railway-edge: railway/asia-southeast1-eqsg3a

 (edge is in Singapore)

My service is deployed in Amsterdam, but requests are being routed through the Asia-Southeast edge. This adds ~100-150ms of unnecessary latency.

Expected behavior: Requests from European users should go through a European edge, not Asia.

Questions:

  1. Why is my edge routing going through Asia when my service is in Amsterdam?

  2. Is there a way to configure edge routing to stay in the same region as my service?

  3. Is this a known issue or temporary infrastructure change?

Thank you for your help!

Solved
pray1

15 Replies

jamiemufu
PRO

a month ago

I am also having this issue funnily enough

cf-ray: LHR
x-railway-edge railway/asia-southeast1-eqsg3a

Service in Amsterdam also.

Railway
BOT

a month 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!

joeberg-positive-sum
PRO

a month ago

also getting the same thing and its really spiking load times (30+ seconds) of static assets like my vendor.js files. my railway service deployed to US East

cf-ray: EWR
x-railway-edge: railway/asia-southeast1-eqsg3a

Anonymous
PRO

a month ago

I'm also seeing the same thing. User is in Washington, USA. Really slowing down requests since yesterday.

```
cf-ray: 9be69baf39377615-SEA

server: cloudflare

x-railway-edge: railway/asia-southeast1-eqsg3a

x-railway-request-id: 9fFTu4xDQ8WI9-8b0ubPiw
```

Railway
BOT

a month ago

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

brody
EMPLOYEE

a month ago

This should be fixed now, can ya'll check again please.

Status changed to Awaiting User Response Railway • about 1 month ago

joeberg-positive-sum
PRO

a month ago

working, thanks brody!

smiley1

Status changed to Awaiting Railway Response Railway • about 1 month ago

Status changed to Solved brody • about 1 month ago

tommyvahabov
PROOP

a month ago

Mine still has 160-330ms, used to have 20-30ms sometimes 40-50

Status changed to Awaiting Railway Response Railway • about 1 month ago

brody

This should be fixed now, can ya'll check again please.

tommyvahabov
PROOP

a month ago

Mine still has 160-330ms, used to have 20-30ms sometimes 40-50ms

tommyvahabov
PROOP

a month ago

railway/us-east4-eqdc4a showing, but in my settings it shows Amsterdam, Netherland. i want it to be Amsterdam please.

Railway
BOT

a month 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!

Status changed to Awaiting User Response Railway • about 1 month ago

sam-a
EMPLOYEE

a month ago

Hi - this should be resolved. Let us know if you are still seeing any routing issues.

The Railway Team

tommyvahabov
PROOP

a month ago

Thanks! Worked.

Status changed to Awaiting Railway Response Railway • about 1 month ago

Status changed to Solved sam-a • about 1 month ago

Railway
BOT

25 days ago

✅ The ticket US-East routing issue for global traffic has been marked as completed.

Railway
BOT

25 days ago

✅ The ticket Edge routing issue for non-US-East traffic has been marked as completed.

Loading...