---
title: "Readiness probe — pod runtime snapshot"
method: GET
path: "/v4/health/ready"
tags: ["Health"]
---

# Readiness probe — pod runtime snapshot

`GET /v4/health/ready`

Always returns HTTP 200. The body carries the pod's rolling 60s runtime window — mean cores against the cgroup quota, responses served, RSS against the memory limit, worst event-loop drift. Nothing here fails the probe yet: the thresholds that would identify a GC-bound pod are not calibrated against production traffic, so this ships as telemetry first. Every window is also logged as `[RUNTIME] window`.

## Response `200`

Response for status 200

- object
  - `cpuCores` number, required
  - `cpuQuotaCores` number
  - `cpuLimitCores` number
  - `cpuLimitBasis` union
    - string
    - string
  - `cpuRatio` number
  - `requestsInWindow` number, required
  - `rssBytes` number, required
  - `rssRatio` number
  - `maxEventLoopLagMs` number, required
  - `windowSeconds` number, required

---

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