Regions & latency
CloudNx runs in a single EU West region today, with an Indian region on the public roadmap.
Available region
| Region | Code | Status | Workloads |
|---|---|---|---|
| EU West | eu-west | Live | All compute, S3 storage, load balancers |
| India South (Mumbai) | in-mum (S3 endpoint label) | Planned · Q3 2026 | Compute + S3 region pair |
Latency from Indian cities
Round-trip-time from major Indian metros to the EU West edge, measured over public internet:
| City | Median RTT | Suitable for |
|---|---|---|
| Mumbai | ~135 ms | Backend APIs, batch jobs, dev environments |
| Bengaluru | ~155 ms | Same as above |
| Hyderabad | ~165 ms | Same as above |
| Delhi | ~185 ms | Same as above |
Realtime workloads:if you need sub-50 ms response times to Indian end-users (chat, gaming, voice), wait for the Mumbai region. EU West is fine for everything else, including video transcode, ML inference, and most B2B SaaS APIs.
What you don’t see
We deliberately don’t expose the underlying datacenter (Hetzner Helsinki) or hypervisor brand to customers. The compliance contract, support relationship, and invoicing are all with CloudNx Technologies(Indian sole proprietorship). Hardware location is documented for transparency but doesn’t change who you’re doing business with.
Multi-region roadmap
The Indian region is gated on hitting ~₹1.5L MRR — bare metal in Mumbai costs roughly 3× European rates, so we won’t commit to it until the unit economics work for both sides. Until then, every customer ships from the same EU West single-tenant box.