a month ago
Dear Railway Support Team,
I am writing to report a persistent performance issue with one of my services deployed in the Singapore region.
Currently, I have several services running on your platform, and while most operate smoothly, one of my specific services is experiencing significant latency when deployed in the Singapore region. Since my application requires a specific geographic origin to function correctly with its external APIs, I must keep this service hosted in Singapore.
I have observed that this particular service becomes extremely slow, making it difficult to perform essential account management and data retrieval tasks. Interestingly, I have other services performing similar operations in the same region that are running without any issues.
Could you please assist me in investigating this? I would appreciate it if you could check if there are any network routing issues, resource constraints, or specific limitations affecting this container or service instance.
Please let me know if there is any information you need from my side to help diagnose the cause of this latency. I look forward to your guidance on how to resolve this.
Best regards
Pinned Solution
a month ago
- Check edge routing 'hairpinning' by inspecting the response headers of a slow request and look for x-railway-edge header
- Make sure all internal calls use *.railway.internal hostname to keep the traffic inside local Singapore network
- Ensure keep-alive and connection pooling are enabled in your HTTP client
- Your service and the database are physically deployed in completely different regions, causing severe cross-region network latency.
2 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
- Check edge routing 'hairpinning' by inspecting the response headers of a slow request and look for x-railway-edge header
- Make sure all internal calls use *.railway.internal hostname to keep the traffic inside local Singapore network
- Ensure keep-alive and connection pooling are enabled in your HTTP client
- Your service and the database are physically deployed in completely different regions, causing severe cross-region network latency.
h701h
1. Check edge routing 'hairpinning' by inspecting the response headers of a slow request and look for x-railway-edge header 2. Make sure all internal calls use *.railway.internal hostname to keep the traffic inside local Singapore network 3. Ensure keep-alive and connection pooling are enabled in your HTTP client 4. Your service and the database are physically deployed in completely different regions, causing severe cross-region network latency.
a month ago
Thank you so much for your valuable input and guidance!
I wanted to update you that I found the root cause of the performance issue. It turned out that the service and the database were deployed in different regions, which caused significant cross-region latency. By aligning both the service and the database to the same region, the latency issue was completely resolved and everything is now running smoothly.
I truly appreciate your support and for pointing me in the right direction!
Status changed to Solved ibowfu • about 1 month ago