Skip to content
Many Chinese ISP paths enter Railway at US/EU edges; HKG/SIN POPs available
panther114
OP

a month ago

We run a real-time drawing game at https://drawbattle.up.railway.app, deployed in Railway Asia Southeast (Singapore). Shanghai probes on China Mobile AS56040 and CERNET2 AS24364 enter at US edges (sjc1, lax1); China Telecom AS4812 enters at Paris (cdg1); a China Unicom consumer hotspot (AS17621) also entered at lax1, while a China Unicom AS9929 probe reached sin1 in 447 ms. The same service answers Hong Kong/Tokyo clients in 78–98 ms, so the app and nearby edges are healthy; the China entry paths are not. We want to keep the existing URL and make no client changes. Please investigate whether Chinese traffic can enter at HKG or SIN, and whether edge steering or IPv6 is available.

Players also report mid-game WebSocket disconnections. We have not determined whether these are edge resets, application heartbeat timeouts, or mobile-network drops. The routing request is the platform-level question; disconnect reports are additional context, not a request to debug application code.

Solved

1 Reply

Railway
BOT

a month ago

Your *.up.railway.app domain is served from anycast IP addresses that are announced from all of our edge POPs at once. Which POP a request enters at depends on how each ISP's BGP routing and peering reach those addresses. Your deployment region has no effect on it, so the China Mobile, CERNET2, China Telecom and China Unicom paths you measured landing in San Jose, Los Angeles or Paris are those carriers' routing choices.

There is no per-service or per-domain setting, and no edge-steering option, that makes Chinese traffic enter at Hong Kong or Singapore. Once a request enters at any POP, it is sent over our internal network to your Asia Southeast deployment. We can't confirm IPv6 entry as a way to change which POP these carriers reach.

To check the path for a specific request, send X-Railway-Debug: 1. The response will show X-Railway-Edge (the POP where it entered) next to X-Railway-Upstream-Zone (the zone that served it). You can also see X-Railway-Edge on every request in your service's HTTP logs, which may help you see whether the mid-game disconnects cluster on the long-haul entry points. The edge networking docs cover these headers and the diagnostic steps.


Status changed to Awaiting User Response Railway • 26 days ago


Railway
BOT

18 days 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 • 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...