Production · independently monitored

Service health

See whether the Core API health endpoint is responding now, then explore public-edge availability and latency collected by Prometheus over time.

Current monitor sample

Checking the Core API…

Reading the latest public-edge health measurement.

StatusCheckingExpected { "ok": true }
Response time—Latest sanitized monitor sample
Upstream response—Waiting for first check
Latest measurement: Checking the Core API…. Response time unavailable. No upstream response available.
Prometheus history

Public-edge availability & latency

Scheduled checks of the public /healthz endpoint, independent of this browser session.

Loading 24 hours of monitoring data

Reading downsampled public-edge measurements from Prometheus.

History starts at probe deployment and reflects public endpoint reachability from the monitoring cluster. It is operational telemetry, not a contractual SLA or incident record.

This browser tab

Recent monitor snapshots

The first monitor snapshot will appear here shortly.

Every 30s

This is not historical uptime monitoring. These monitor snapshots exist only while the page is visible and disappear when the tab closes; use Prometheus history above for persisted measurements.

Open /healthz
What this check proves

The public-edge probe verifies that the production Core API process health endpoint is reachable and returns its documented healthy payload. It does not test databases, crawlers, integrations, or other downstream dependencies.