> For the complete documentation index, see [llms.txt](https://docs.flowcp.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowcp.ai/reference/system-status.md).

# System status

The system status page shows the real-time health of every FlowCP service component.

## URL

```
https://app.flowcp.ai/status
```

The page is publicly accessible — no login required. Share it with your team or bookmark it to check during incidents.

## What it shows

| Service         | What is checked                                                |
| --------------- | -------------------------------------------------------------- |
| **API**         | The control-plane API process is running and handling requests |
| **Database**    | PostgreSQL is reachable and responding to queries              |
| **Redis Cache** | Redis is reachable and responding to pings                     |
| **MCP Runtime** | The MCP protocol server is running and accepting connections   |

Each service card displays:

* **Status badge** — Operational, Degraded, or Outage
* **Latency** — Round-trip time for the health check in milliseconds
* **Error message** — Shown only when a service is degraded or down

## Status levels

| Status                      | Meaning                                                      |
| --------------------------- | ------------------------------------------------------------ |
| **All Systems Operational** | All services are healthy                                     |
| **Partial Degradation**     | One or more services are responding slowly or intermittently |
| **Major Outage**            | One or more services are unreachable                         |

## Auto-refresh

The page re-checks all services every **30 seconds** automatically. You can also click **Refresh** to trigger an immediate check.

## Programmatic health check

The underlying health endpoint is available at:

```
GET /api/health
```

Example response:

```json
{
  "service": "api",
  "status": "ok",
  "checkedAt": "2026-06-02T12:00:00.000Z",
  "services": {
    "api": { "status": "ok", "latencyMs": 0 },
    "database": { "status": "ok", "latencyMs": 4 },
    "redis": { "status": "ok", "latencyMs": 1 },
    "mcpRuntime": { "status": "ok", "latencyMs": 8 }
  }
}
```

The endpoint always returns HTTP 200 so that load balancers remain satisfied even when individual dependencies are degraded. Check the `status` field in the response body to determine overall health.