15 days ago
Dear Cloud Support Team,
We are currently using your services in the India (Mumbai) region and have observed that API requests are taking significantly more time than expected. This latency is impacting our application performance and overall user experience.
We suspect that the issue may be related to network performance or routing in this region. As our use case requires low latency and a strong, stable network connection, we would like your assistance in investigating this matter.
Could you please help us with:
Confirmation of any known latency or network issues in the Mumbai region
Recommendations for improving API response times
Any configuration changes or service upgrades that could provide stronger network performance
We appreciate your support and look forward to your guidance on resolving this issue at the earliest.
Thank you.
Best regards,
Gurunath Gutade
3 Replies
14 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 14 days ago
14 days ago
First of all railway didn't provide India (Mumbai) network region. If you use any external service and pass into here then Singapore is the best choice and it has lowest latency among all regions
14 days ago
up for solution
14 days ago
To clarify what error403op said: Railway does NOT have an India (Mumbai) region. The available regions are US West, US East, EU West, and Asia Pacific (Singapore). There is no GCP asia-south1 (Mumbai) on Railway.
So if your service is deployed on Railway and your users are in India, the closest available region is Singapore (asia-southeast1). This is a known geographical limitation — Railway doesn't currently offer an Indian data center.
What you can do to reduce latency for Indian users:
1. Deploy your Railway service in the Singapore region if you haven't already — it will be significantly faster than US/EU regions for Indian traffic
2. If you need Mumbai-level latency, consider putting a CDN or reverse proxy (e.g. Cloudflare) in front of your Railway service — Cloudflare has Mumbai PoPs and can cache/route requests closer to users
3. For latency-critical workloads that strictly need Mumbai, you may need a hybrid setup where Railway handles the backend logic but a Mumbai-region proxy (Cloudflare Workers, etc.) handles the edge
If you want Railway to add an India region, you can submit a feature request at station.railway.com/feedback.