# Service Status

![Service Statuses](/files/-M3RpPG0zwm4XBlkuj5r)

## Indicators

### Down

Services shown in the Down state indicate that there are 0 service instances announcing into the mesh. This would be seen anytime the service is no longer deployed (scaled to 0) but has not been removed from [catalog](/grey-matter-documentation/usage/sense/catalog.md). Additionally, this can be seen if the catalog entry doesn't properly match the announced service information.

![Service Down](/files/-M3RrFBd6kDxw8SBuaoR)

### Warning

The warning state indicates that a service has been under or over provisioned within the mesh. The acceptable provisioned range is set with the `minInstances` and `maxInstances` field of the [Catalog service entry](/grey-matter-documentation/usage/sense/catalog.md#service-entry)

![Service Warning](/files/-M3RrFBhNp7Ztf1CU0KH)

### Stable

Services in a stable state have no known issues with their deployment.

![Service Stable](/files/-M3RrFBnfy98R3DJR3kP)

## Troubleshooting

If a service appears to be in an incorrect state in the dashboard, try the following troubleshooting methods.

* Make sure the `clusterName` field on the [Catalog service entry](/grey-matter-documentation/usage/sense/catalog.md#service-entry) matches the [`name` field](/grey-matter-documentation/usage/fabric/api/cluster.md#name) on the `cluster` object.
* Check the [`CONTROL_SERVER_0_REQUEST_CLUSTER_NAME`](/grey-matter-documentation/setup/sense/catalog.md#control) environment variable. Catalog uses this request cluster to discover instances of services running in the mesh, so if the request cluster doesn't know about the target cluster you're troubleshooting, Catalog won't see any instances of it either. You can test this by curling the [`/clusters`](https://www.envoyproxy.io/docs/envoy/latest/operations/admin#get--clusters) endpoint of the request cluster's admin server. If you don't see the target cluster listed with an IP address, make sure that routing between the request cluster and the target cluster is correct.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://greymatter.gitbook.io/grey-matter-documentation/usage/sense/servicestatus.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.