+1 Very much needed in Bangalore or Mumbai region

super needed ++

@angelo, this is a chicken and egg problem. I'm a founder and I won't be on Railway if Indian region isn't there and hence you won't traction on such threads. Indian regulations demand servers be in India.

Hello,

Upvoting feedback threads helps show demand even if you're not currently using the platform, so that over time, with sufficient interest, we could consider adding an Indian region.

However, with the current level of demand shown, this won't be feasible for the foreseeable future.

Best regards,

Brody

Roughly how much demand is required for it to be considered?

it would be nice have in India as well. I heard the DC cost is cheaper in India, than in singapore

For Indian customers, Singapore is still far away and the latency penalty is felt for northern India users.

Yes. Frequent issues of slow connection for my team based in India.

I'm sorry, but do you really think someone would create an account to just upvote? This page barely even shows up on Google.

Besides what % of your users engage here at all?

This is a terrible way to gauge interest - should probably have an interest form on your resources page and near the dropdown for selecting the region. Much better way to understand what regions people actually need/want.

I work on contract, developing MVPs and internal tools for various companies - when working on an India-centric project, there are data localisation laws. Can't use Railway, even if the most sensible option for the project otherwise. What do I do - ignore and move on (I don't go around looking for a way to tell you that I needed something you don't offer).

Didn't even know this thread existed and I came here by accident looking for something else.

Folks, India is a big market. Tons of companies who required cloud infra. Makes sense to be here. Singapore won't cut it.

I took the decision of moving from railway to digital ocean as the data center is close by india.

Only reason was the latency to singapore datacenter for my indian customers.

Otherwise i love railway.

i did a test with hosting application in railway and render - both in singapore region with supabase database in mumbai region, i did a load test to understand the request and response time, devoid of the api calls and realised that render is better performance than railway.

For some reason, req per second for railway was double the time of render.com. Same App.

That being said, i really like railway's experience and freedom to deploy the entire application. I tried one click deployment of supabase and really liked it as well.

But a higher "req per second" is better. Indicating Railway performed better.

apologies for the confusion, i meant to say render had higher requests per second compared to railway. Thanks for the request of clarification

+1

received a request from our India customer to have better latency. App is max optimized, only obvious place to save time is to save the trip to Singapore server. Would have to move out this app to AWS. This increases cost for us and more work too, but this is a big customer for us.

Plus there are 10 deployments that are still running in AWS Mumbai because Indian data laws require data server to be the physically present in India.

Indian government has also announced a tax break for data centers in India:

https://etedge-insights.com/in-focus/budget-2026/union-budget-2026-signals-a-data-centre-led-growth-story-for-india-inc/amp/

We urgently require an Indian region for deployment. Initially, we chose Singapore as the latency difference was negligible at that stage. However, as our application has scaled significantly, the increased delays are now severely impacting user retention.

At this point, migrating to another PaaS or VPS provider is not a feasible option for us. Introducing an Indian region would greatly improve performance for our growing user base and would be highly beneficial.

If there was ever a time to consider adding an Indian region, it is now.

@brody, any change is Railway's plans with India region?

My previous message from 6 months ago holds true.

@brody

Thanks for the response.

I just want to clarify, is the decision to add an Indian region primarily based on the number of upvotes on this thread?

If so, that may not fully reflect actual demand. Many teams (especially Indian startups and agencies) don’t actively monitor or engage in feedback threads, but they do make infrastructure decisions based on latency and data localisation requirements.

For example:

• Indian data localisation laws require physical hosting within India for certain use cases.

• Latency from Singapore is becoming a real issue as applications scale.

• Several users in this thread have already migrated to providers like AWS Mumbai or DigitalOcean Bangalore purely due to region availability.

In our case, moving away from Railway would be a business decision driven only by region constraints, not product quality.

Would Railway consider a more structured way to gauge demand (interest form, region request counter in dashboard, waitlist, etc.)? I suspect the real demand may be significantly higher than this thread suggests.

India is one of the fastest-growing startup ecosystems globally, and having a region here could unlock substantial long-term growth for Railway.

Happy to provide usage projections or connect you with other teams who would benefit.

folks, have been waiting for india region for a great while now, kept on sg but now the time is up. Client seeing 600ms roundtrips unnecessarily and want us to cater for latency more than anything.

hi.. India localization is strongly needed. we will not have choice but to move away due to regulatory reasons and not the product reason. please consider this.

Debugged this a bit. Currently Singapore is the WORST place to host your apps since for some reason it travels all the way to USA and then to singapore causing the 600ms latency which is extremely stupid. Housing it in USA gives a 500ms.

Current best solution to solve the Latency problem (not the governance issues), is to have it in Singapore + setup Cloudflare Proxied CDN. That routes better and you get a 200ms latency.

Hope this helps someone. Honestly, having to do this manually beats the purpose of using Railway

Need India region 🚀

Vry much needed else we are forced to move away due to the DPDP act and we have our entire platform on railway and are demanding things regarding data residency etc

Im requesting @brody to please add Indian Region

Agree. Love the platform but need India region otherwise we will have to move away

@brody or @angelo-railway , we want Indian Region , Please add that , it would be very helpful. Please consider

To be completely transparent, given the current level of demand, this won't be feasible for the foreseeable future.

@brody You can close this thread and completely deny adding an Indian region if that’s the decision. But please don’t use this thread as the sole metric for measuring demand.

If Railway genuinely wants to understand the demand, there are much better ways to measure it:

• Create an X poll asking Railway users whether they need an India region.
• Send an email to Railway users asking whether an India region would affect their hosting decision.
• Add an India-region interest/waitlist option inside the dashboard.

Then, if there’s still not enough traction, I can guarantee you probably won’t hear people asking for an Indian region again.

But please don’t conclude that there isn’t enough demand simply because this forum thread doesn’t have enough upvotes or comments.

A lot of Indian startups and teams simply don’t follow Railway’s feedback forum. They just quietly move to AWS Mumbai, DigitalOcean Bangalore, or another provider when region availability becomes a requirement.

I genuinely like Railway and would prefer to stay, but for many of us this is becoming an infrastructure/business requirement rather than a feature request.

Please measure the actual demand before deciding there isn’t enough of it.

@brody This is exactly why I don't think this thread should be treated as the metric for demand.

https://feedback.render.com/features/p/mumbai-region

Look at Render's Mumbai-region request — it was created around 2020, was marked planned, and yet years later people are still asking for an update.

Is the conclusion supposed to be that there is no demand for an Indian region, or that feedback threads simply aren't a reliable way to measure it?

I genuinely don't want Railway to keep the India region in the same cycle for the next 5–6 years.

If the actual answer is “we are not going to build an Indian region,” that's completely fine — just say that clearly and we can make our infrastructure decisions accordingly.

But if the decision is based on demand, please measure the demand directly.

Put up an X poll. Send an email to Indian Railway users. Add an “Interested in India Region” button/waitlist in the dashboard.

Give the actual users a chance to tell you.

And if after doing that there still isn't enough demand, then fair enough — close the request and move on.

But please don't conclude that there is no demand simply because this particular forum thread doesn't have enough activity.

Otherwise, we may be having this exact same conversation in 2030.

If your measure demand primarily through feedback-board votes/comments, India may remain stuck in a loop:

Not enough votes → India region not prioritized → Indian customers migrate elsewhere → fewer Railway/Render users in India → apparently low demand → India region not prioritized

@brody @angelo-railway

Relying on feedback thread upvotes as the sole metric for regional demand is a fundamentally broken signal. Most active developers, agencies, and founders in India don't spend their time browsing support forums to upvote feature requests—they are deploying code.

If you want the true picture, look at your own internal analytics: check user account origins, IP login locations, billing regions, and traffic routes. India has one of the largest developer and startup ecosystems globally, and a significant portion of your active traffic is already originating from here.

To give you a real-world technical dealbreaker: I am building real-time Voice AI agents. In voice applications, sub-100ms latency is non-negotiable for fluid, human-like interaction. Hosting in Singapore forces roundtrip delays of 200ms to 600ms due to suboptimal routing, completely breaking the user experience.

We love Railway's DX and want to build here, but for real-time applications (Voice AI, WebSockets, streaming) and data compliance (DPDP Act), Singapore is simply not viable. Developers aren't waiting around on this forum; when latency hits a bottleneck, they quietly migrate their workloads to AWS Mumbai, GCP, or DigitalOcean Bangalore.

Please evaluate actual user telemetry, dashboard traffic, or run a direct dashboard inquiry rather than writing off an entire market based on forum votes. The demand is already on your platform—you are just losing the scaling revenue.

+1 Very much needed in Bangalore or Mumbai region

I agree

yes