Could you confirm where the impacted users are connecting from?

If they're connecting from the US, the edge network is correct (see https://docs.railway.com/reference/edge-networking for more details).

If they're connecting from Asia and seeing railway/us-west2 as the edge response, please have them follow the instructions at https://docs.railway.com/reference/network-diagnostics and share the results of the diagnostics here.

I tested this myself in Asia. Here is diagnosis results.

Railway Network Diagnostics

Generated : Monday, Feb 2 2026 22:01:31 CST

Endpoint : routing-info-production.up.railway.app

-------------------------------------------------------------------------------

Client IP Info

-------------------------------------------------------------------------------

{

"ip": "221.220.135.254",

"city": "Beijing",

"region": "Beijing",

"country": "CN",

"loc": "39.9075,116.3972",

"org": "AS4808 China Unicom Beijing Province Network",

"postal": "100000",

"timezone": "Asia/Shanghai",

"readme": "https://ipinfo.io/missingauth"

}

-------------------------------------------------------------------------------

HTTP HEAD request

-------------------------------------------------------------------------------

Error: making HTTP HEAD request: Head "https://routing-info-production.up.railway.app": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

-------------------------------------------------------------------------------

DNS lookup (using system DNS)

-------------------------------------------------------------------------------

��Ȩ��Ӧ��:

������: UnKnown

Address: fe80::1

����: routing-info-production.up.railway.app

Address: 66.33.22.232

-------------------------------------------------------------------------------

DNS lookup (using Cloudflare)

-------------------------------------------------------------------------------

��Ȩ��Ӧ��:

������: one.one.one.one

Address: 1.1.1.1

����: routing-info-production.up.railway.app

Address: 66.33.22.232

-------------------------------------------------------------------------------

Traceroute

-------------------------------------------------------------------------------

ͨ������ 30 ��Ծ������

�� routing-info-production.up.railway.app [66.33.22.232] ��·��:

1 17 ms 16 ms 31 ms bogon [192.168.1.1]

2 7 ms 6 ms 6 ms 221.220.128.1

3 41 ms 5 ms * 61.51.175.229

4 * * * ������ʱ��

5 6 ms * * 219.158.8.74

6 * * * ������ʱ��

7 250 ms 228 ms 232 ms 219.158.7.122

8 276 ms * * lax-b3-link.ip.twelve99.net [80.239.134.246]

9 309 ms 299 ms 319 ms lax-bb2-link.ip.twelve99.net [62.115.126.248]

10 318 ms 318 ms 342 ms palo-bb2-link.ip.twelve99.net [62.115.137.206]

11 * * 362 ms sjo-b23-link.ip.twelve99.net [62.115.139.117]

12 367 ms 349 ms 336 ms railwaycorp-ic-390075.ip.twelve99-cust.net [62.115.196.225]

13 352 ms 312 ms 288 ms 66.33.22.232

�������ɡ�

-------------------------------------------------------------------------------

Ping (n=10)

-------------------------------------------------------------------------------

���� Ping routing-info-production.up.railway.app [66.33.22.232] ���� 32 �ֽڵ�����:

������ʱ��

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=325ms TTL=45

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=365ms TTL=45

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=359ms TTL=45

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=355ms TTL=45

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=369ms TTL=45

������ʱ��

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=362ms TTL=45

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=297ms TTL=45

���� 66.33.22.232 �Ļظ�: �ֽ�=32 ʱ��=394ms TTL=45

66.33.22.232 �� Ping ͳ����Ϣ:

���ݰ�: �ѷ��� = 10���ѽ��� = 8����ʧ = 2 (20% ��ʧ)��

�����г̵Ĺ���ʱ��(�Ժ���Ϊ��λ):

���� = 297ms��� = 394ms��ƽ�� = 353ms

Completed

Thanks for your help!

Hello Xiaomi,

Unfortunately, we’re currently unable to tune our network to reliably support connectivity within China. Due to the way ISPs operate there, we have limited control over routing paths, which makes compatibility difficult.

I’m sorry this isn’t the outcome you were hoping for. It’s something we may explore improving in the future, but at the moment we’re unable to offer a solution.

Understood, thanks!

✅ The ticket Routing issue in Singapore region has been marked as completed.