> For the complete documentation index, see [llms.txt](https://docs.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neevcloud.com/neevcloud-products/availability-zones.md).

# Availability Zones

Availability Zones (AZs) are geographically separated data center locations within a NeevCloud region. Each zone operates on independent power, cooling, and networking infrastructure, ensuring that a failure in one zone does not affect others in the same region. Users can choose their preferred availability zone based on performance, redundancy, or disaster recovery requirements. Deploying resources across multiple zones provides fault isolation, high availability, and a foundation for disaster recovery.

***

### **Available Regions and Zones**

NeevCloud currently operates across two regions in India:

**Central India** Designed for low-latency workloads with stable and consistent network performance. Well-suited for government, enterprise, and analytics applications.

**West India** Built for strong connectivity and redundancy with reliable uptime. Well-suited for finance, e-commerce, and media applications.

***

### **Selecting an Availability Zone**

When launching a server, you can specify a region and availability zone during instance configuration:

1. Log in to the NeevCloud Console.
2. Navigate to **Compute → Servers** and click **Launch Instance**.
3. Under the **Location** section, select a region and preferred availability zone.
4. Choose an operating system or marketplace image.
5. Complete the remaining configuration — flavor, networking, and security groups.
6. Click **Launch Instance** to deploy.

<figure><img src="/files/oBd9fIVKwcYe6C4fwhHs" alt=""><figcaption></figcaption></figure>

***

### **Use Cases**

Availability Zones support a range of deployment strategies:

* **Multi-tier applications** — Distribute web, application, and database layers across zones to eliminate single points of failure.
* **Disaster recovery** — Replicate critical workloads to a secondary zone or region to maintain continuity during outages.
* **Performance-sensitive workloads** — Place compute resources closer to end users to reduce latency.