Service status and operational checks.
Use the public health endpoint for a current front-door check, then narrow a problem to the affected project, offering, or upstream provider.
Front-door health.
The machine-readable /health endpoint checks whether the shared cohesivity front door is serving requests. An HTTP 200 confirms that route responded at that moment. It does not prove that every tenant resource, tenant runtime, or third-party provider is healthy, so use the affected offering endpoint when you need a narrower check.
open the health endpointDiagnose without exposing credentials.
Retry only when the response says it is safe, and preserve the HTTP status, approximate UTC time, endpoint, offering name, and request identifier. Do not paste management keys, application keys, OAuth tokens, provider credentials, payment details, or environment values into a report. The API documentation describes structured errors, retry delays, version headers, and quota signals that an agent can use before escalating.
Current reporting limits.
cohesivity does not currently publish an uptime guarantee, incident-history feed, emergency phone line, or response-time promise on this page. If the health endpoint responds but a project operation still fails, contact the team from the account email when possible and include only the safe diagnostic fields above.