From f35f9700e22ece80dffc285701dd13b1e89b52c6 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 31 Oct 2026 07:40:07 +0000 Subject: [PATCH] docs(resources): point the hosted status link at status.objectos.ai Support and FAQ linked status.objectstack.ai, which serves nothing. The hosted status page is now built by the cloud heartbeat Worker and lives on the product's own domain, status.objectos.ai. Support's line drops "package registry": the page covers ObjectOS Cloud only. Locale siblings are left to the translation pass (AGENTS.md). Part of objectstack-ai/cloud#3394 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01QUs3BsfhT8srv5D1MTECjw --- content/docs/resources/faq.mdx | 2 +- content/docs/resources/support.mdx | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/content/docs/resources/faq.mdx b/content/docs/resources/faq.mdx index 79405146..4e11d3dc 100644 --- a/content/docs/resources/faq.mdx +++ b/content/docs/resources/faq.mdx @@ -218,7 +218,7 @@ For a self-managed (Enterprise) deployment, status is your concern — point your monitor at `/api/v1/health` for liveness and `/api/v1/ready` for readiness, the pair [Docker](/docs/deploy/docker) and [Kubernetes](/docs/deploy/kubernetes) wire up. For hosted services, see -[status.objectstack.ai](https://status.objectstack.ai). +[status.objectos.ai](https://status.objectos.ai). ### What metrics should I monitor? diff --git a/content/docs/resources/support.mdx b/content/docs/resources/support.mdx index 09677005..d149a94f 100644 --- a/content/docs/resources/support.mdx +++ b/content/docs/resources/support.mdx @@ -74,8 +74,9 @@ The underlying ObjectStack framework is Apache-2.0 and accepts contributions: ## Status & incidents -Hosted services (ObjectOS Cloud, package registry): -[status.objectstack.ai](https://status.objectstack.ai). +Hosted ObjectOS Cloud: +[status.objectos.ai](https://status.objectos.ai). It shows each monitored +service's state and last check, and any incident notice we post. For your self-hosted ObjectOS deployment, status is your concern — wire it to your normal monitoring (see [Observability](/docs/operate/observability)).