Skip to content
Traffic from India routing via Sao Paulo edge despite Singapore service region
kritovain
OP

2 months ago

Project: rare-patience

Service: bizos

Service region: Southeast Asia (Singapore)

Public domain: bizos-production-80f0.up.railway.app

Client location: Noida, India

Issue: All requests from India land on the Sao Paulo edge (x-railway-edge: gru1) instead of an Asian edge. This adds roughly 1.2 seconds to every request.

A traceroute shows round-trip time jumping from about 7ms at hop 4 to about 140ms at hop 5 and about 270ms at hop 6. The Railway edge IP 69.46.46.79 answers at about 270ms. TCP connect plus TLS alone takes about 0.58 seconds.

Database query latency measured inside the container is 64ms, so the delay is entirely in edge routing, not the application.

Can Indian traffic be routed to a nearer edge?

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 2 months ago


2 months ago

We had just made a change to this. If you aren't already seeing improvements, could you follow the steps in our network diagnostics guide and also include your deployment ID (from the Railway dashboard) and the X-Railway-Upstream-Zone header value (send X-Railway-Debug: 1 with a request to capture it)? You can post the report here.


Status changed to Awaiting User Response Railway • 2 months ago


Railway
BOT

2 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 • 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...