> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/2026.4/getting-started/self-hosted/airctl/viewing-and-checking-region-status.md).

# Viewing and Checking Region Status

This section explains how to list all deployed regions in <code class="expression">space.vars.product\_name</code> and check their current deployment status using the `airctl` CLI tool.

## List All Deployed Regions

To view the list of all regions currently deployed in the Self-Hosted version of <code class="expression">space.vars.product\_name</code> , run:

{% tabs %}
{% tab title="Bash" %}

```bash
/opt/pf9/airctl/airctl get-regions --config /opt/pf9/airctl/conf/airctl-config.yaml
```

{% endtab %}
{% endtabs %}

This command retrieves region names directly from the state file and lists all currently active regions. Use it to confirm which regions are available before performing operations such as backups, deletions, or status checks.

Example output:

{% tabs %}
{% tab title="Bash" %}

```bash
$ /opt/pf9/airctl/airctl get-regions --config /opt/pf9/airctl/conf/airctl-config.yaml 
Deployed Regions:
• Infra
• LON
```

{% endtab %}
{% endtabs %}

## Check Region Status

The `airctl status` command provides detailed information about the health and service status of each region.

By default, it shows the status of all deployed regions, including service counts and readiness indicators.

### Status Command Flags

The `airctl status` command supports the following flags to customize output:

* \--region : Specifies which region’s status to display. **This flag is mandatory** when using `--ready` or `--desired`.
* \--ready: Displays **only the number of Ready services** for the specified region.
* \--desired: Displays **only the number of Desired services** for the specified region

{% hint style="info" %}
**Info**

* The `--ready` and `--desired` flags are **mutually exclusive** — only one can be used at a time.
* When used, these flags print **only the number of services** in the specified state for the given region.
  {% endhint %}

{% tabs %}
{% tab title="Bash" %}

```bash
Usage:
  airctl status [flags]

Flags:
      --desired         Show only the number of desired services for each region
  -h, --help            help for status
      --ready           Show only the number of ready services for each region
  -r, --region string   Display status for a specific region

Global Flags:
      --config string   config file (default is $HOME/airctl-config.yaml)
      --json            json output for commands (configure-hosts only currently)
      --quiet           disable spinners
      --verbose         print verbose logs to the console
```

{% endtab %}
{% endtabs %}

### Examples:

View All Regions and their Status :

{% tabs %}
{% tab title="Bash" %}

```bash
$ /opt/pf9/airctl/airctl status --config /opt/pf9/airctl/conf/airctl-config.yaml
------------- deployment details ---------------
fqdn:                airctl-1-4161345-238.platform9.localnet
region:              airctl-1-4161345-238
deployment status:   ready
region health:       ✅ Ready
version:              PCD 2025.10-69
-------- region service status ----------
desired services:     30
ready services:       30


------------- deployment details ---------------
fqdn:                airctl-1-4161345-238-lon.platform9.localnet
region:              airctl-1-4161345-238-lon
deployment status:   ready
region health:       ✅ Ready
version:              PCD 2025.10-69
-------- region service status ----------
desired services:     84
ready services:       84
```

{% endtab %}
{% endtabs %}

View status for a specific region :

{% tabs %}
{% tab title="Bash" %}

```bash
$ /opt/pf9/airctl/airctl status --config /opt/pf9/airctl/conf/airctl-config.yaml --region Infra
------------- deployment details ---------------
fqdn:                airctl-1-4161345-238.platform9.localnet
region:              airctl-1-4161345-238
deployment status:   ready
region health:       ✅ Ready
version:              PCD 2025.10-69
-------- region service status ----------
desired services:     30
ready services:       30
```

{% endtab %}
{% endtabs %}

View Ready Services for a Region :

{% tabs %}
{% tab title="Bash" %}

```bash
$ /opt/pf9/airctl/airctl status --config /opt/pf9/airctl/conf/airctl-config.yaml --ready --region LON
84
```

{% endtab %}
{% endtabs %}

View Desired Services for a Region :

{% tabs %}
{% tab title="Bash" %}

```bash
$ /opt/pf9/airctl/airctl status --config /opt/pf9/airctl/conf/airctl-config.yaml --desired --region LON
84
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/private-cloud-director/2026.4/getting-started/self-hosted/airctl/viewing-and-checking-region-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
