All releases
Mohith / 3 min read
OperationsAvailable
Public status and safer operational errors
Public component status and incident feeds arrived alongside a shared contract that separates user errors from internal diagnostics.
Mohith / 3 min readWhat changed
The public status surface exposes current components, incident history, maintenance windows, and machine-readable JSON and RSS outputs.
Operational error handling now passes through a shared contract so public responses stay useful without echoing secrets or internal failure detail.
Two audiences, two levels of detail
Users receive a stable public error and a request context they can report. Operators retain structured diagnostics in protected logs, with sensitive values removed before serialization.
Status is not authentication state
A healthy component report describes service availability. Applications must still validate sessions, authorization, and response contracts on every protected request.