diff --git a/content/docs/resources/faq.mdx b/content/docs/resources/faq.mdx
index 7940514..4e11d3d 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 0967700..d149a94 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)).