Production status / evidence boundary
Current health is read from the running services.
The API and web services expose narrow health endpoints over TLS. A successful response establishes reachability and dependency readiness at that moment; it is not a historical uptime guarantee.
Read the current API health at api.invarent.com/v1/healthz and web health at app.invarent.com/healthz. Customer-specific incidents, degraded workflows, and contracted notifications are handled through the authenticated support record.
Public API health
The endpoint reports application readiness and managed PostgreSQL reachability without disclosing secrets, topology, tenant data, or internal diagnostics.
Portal health
The web endpoint reports service identity and the deployed release SHA so customers and operators can distinguish reachability from release parity.
Workflow and provider state
Durable workflows, billing providers, email delivery, and customer-specific integrations can fail independently of the public web process. Those conditions require scoped operational evidence and case communication.
Incident record
Material incidents are recorded with detection time, scope, customer impact, containment, recovery evidence, and follow-up actions. Public disclosure depends on verified impact and notification obligations.
Next action