Help Center/Admin Operations/Read API Health
Admin Operations•Last updated: 2026-10-20•3 min read

Read API Health

API Health combines signals the platform already records: error events of the last 24 hours, durability-mirror failure counters of this server process, price provider health, the last price refresh run and live probes of two public endpoints.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

Open "System Operations" and click "API Health" (address /admin/system/api-health).

2

Read the tiles

"Diagnostic events (24h)", "Error events (24h)", "Mirror failures (this process)", "Mirror writes landed (this process)", "Last price refresh" and "Self-probes".

💡 Pro Tip: Mirror counters live in the memory of the server process that answered, so they restart from zero after a deployment.
3

Read the table

The "Signal" column says where a row comes from: Self-probe (with latency), Errors, last 24h (one row per route with errors), Durability mirror (per subsystem) and Price provider.

4

Filter

Use the Status filter: OK, FAILING, UNKNOWN or INFO.

Expected Operational Outcome

You see which routes are throwing errors, whether any durable write failed to reach the database, and whether the public endpoints answer.

Troubleshooting & Failure Modes

Symptom: Self-probes show UNKNOWN
Likely Cause: The server has no configured public address (NEXT_PUBLIC_APP_URL) to probe.
Resolution: Ask the platform owner to set it on the deployment.

Was this guide helpful?

Help us refine our platform documentation