Runtime Health
Connect uptime checks to the public web runtime.
The monitoring page shows which lightweight routes are suitable for health, live and ready probes.
Monitoring workflow
Primary health
Monitoring
Public health endpoints for uptime checks.
Use these endpoints to monitor the Zektrx public web runtime. They are intentionally lightweight, noindex, and available during maintenance mode for operational checks.
Public runtime
Operational status
Connect machine-readable health probes with human status, support and recovery routes.200Health
JSONStatus
NoindexUtility
Quick Answer
Monitor the public web runtime from stable endpoints.
This page lists the lightweight health, readiness, liveness and status endpoints used to check www.zektrx.com. It does not monitor app.zektrx.com.
Use /health as the default public uptime target.
Use /status.json when monitors need structured status and support routes.
Use /status when humans need incident, maintenance or contact context.
GET, HEAD
/healthPrimary health
Best default endpoint for uptime monitors and public web runtime checks.
GET, HEAD
/healthHealth alias
Health-check target that returns a direct 200 runtime response.
GET, HEAD
/liveLive probe
Direct 200 responder for simple liveness probes.
GET, HEAD
/readyReady probe
Direct 200 responder for readiness-style probes of the public web runtime.
GET, HEAD
/pingPing probe
Direct 200 responder for lightweight ping checks.
GET, HEAD
/status.jsonMachine status
Structured service status, monitor aliases and support routes.
Related Operations Pages
Connect health checks with human support routes.
Monitoring endpoints serve automated checks, while these pages provide status, security, installation and support information for people.
Status
Human-readable status, incidents and communication routes.
Support
Billing, setup, integration and help routes for users.
Security
Security, vulnerability reporting and trust information.
Install
PWA installation guidance for supported browsers and devices.
Offline
Recovery route when a browser loses reliable network access.
Site utilities
Machine-readable list of utility endpoints.
LLMs index
Curated marketing-site index for AI assistants.
Sitemap index
Technical index of public Zektrx pages.
Monitoring And Recovery
Link machine checks to the recovery path.
Connect automated health checks with status, support, installation and offline guidance so the team can respond quickly.
1
Runtime Health
Primary health
2
Human Status
Status
3
Recovery Context
Offline
Human Status
Give support teams a clear escalation route.
Structured endpoints point back to status, support and recovery pages when humans need context.
Monitoring workflow
Status
Recovery Context
Keep install and offline routes close to incidents.
Connect uptime checks with offline recovery and support so operators have the context needed to respond.
Monitoring workflow
Offline
Monitoring Overview
Machine checks connected to human response.
Use the endpoint, status feed, support guidance and recovery information together as one operating model.
1
Default probe
/health
Give uptime monitors a stable public target for lightweight checks.
2
Structured state
/status.json
Expose machine-readable status, aliases and support routes from one endpoint.
3
Human path
/status
Route people to status, maintenance and incident context when a check needs action.
4
Recovery
Install / offline
Keep app install, offline and support routes close to operational troubleshooting.
Monitor To Support
Connect machine checks with human recovery routes.
Monitoring endpoints are useful because they point to the next action: confirm public health, open the status page, route support and keep recovery paths visible.
Route the issue
Give teams a clear path to status, support, recovery or security without hunting through the site.
Protect the record
Keep operational guidance connected to the documents, evidence and controls that matter on live work.
Return to work
Help users get back to the app, the right page or the right contact route with less friction.