---
title: "Check HTTP Server Status"
method: GET
path: "/health/alive"
tags: ["metadata"]
---

# Check HTTP Server Status

`GET /health/alive`

This endpoint returns a HTTP 200 status code when Ory Oathkeeper is accepting incoming
HTTP requests. This status does currently not include checks whether the database connection is working.

If the service supports TLS Edge Termination, this endpoint does not require the
`X-Forwarded-Proto` header to be set.

Be aware that if you are running multiple nodes of this service, the health status will never
refer to the cluster state, only to a single instance.

## Response `200`

Ory Oathkeeper is ready to accept connections.

- object
  - `status` string, required — Always "ok".

## Other responses

- `default` — Unexpected error

## Changes

- **2023-04-14** `ac46e6738047` — 1 info
  - removed the non-success response with the status `500`
- **2022-02-08** `4a4308530ea1` — 5 info
  - api operation id `isInstanceAlive` removed and replaced with `isAlive`
  - api tag `metadata` added
  - api tag `api` removed
  - added the media type `application/json` for the response with the status `200`
  - …1 more
- **2021-04-26** `26e7abf193b0` — 1 breaking, 4 info
  - removed the media type `application/json` for the response with the status `200`
  - api operation id `isAlive` removed and replaced with `isInstanceAlive`
  - api tag `api` added
  - api tag `metadata` removed
  - …1 more

[Change history](https://skmtc.dev/ory/apis/ory-oathkeeper-api/changes/health/alive/get.md)

---

[API](https://skmtc.dev/ory/apis/ory-oathkeeper-api.md) · [All operations](https://skmtc.dev/ory/apis/ory-oathkeeper-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ory/ory-oathkeeper-api/revisions/3a8f56666af1/schema)