> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alterscope.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Status

> How to check whether the Alterscope API is up, and how operational issues are communicated.

There is not yet a public status dashboard. In the meantime, here is how to check service health and reach us about an issue.

## Check liveness yourself

The API exposes a public health endpoint:

```bash theme={null}
curl -s https://api.alterscope.org/v1/health
```

A `200` response means the API is serving; the body `status` field reports `"healthy"` (or `"degraded"` if a backend check is failing, still `200`). If you get a non-200 or a timeout, the request didn't reach a healthy instance.

Every response also carries its own freshness and quality metadata, so you can tell whether the *data* behind a specific call is current even when the API itself is up — see [Freshness & quality](/trust/data/freshness-and-quality).

## Reporting an issue

If you're seeing errors or degraded responses, [contact support](/resources/support) with the `request_id` from the affected response (also returned as the `X-Request-ID` header) so we can trace the exact calls. See [Errors](/develop/get-started/errors) for where to find it.

## Service levels

How uptime and incident commitments work by plan is on the [Service Level Agreement](/operations/sla) page.