diff --git a/.github/upstream-projects.yaml b/.github/upstream-projects.yaml
index e70d00a1..5929faf8 100644
--- a/.github/upstream-projects.yaml
+++ b/.github/upstream-projects.yaml
@@ -20,7 +20,7 @@
 projects:
   - id: toolhive-registry-server
     repo: stacklok/toolhive-registry-server
-    version: v1.4.9
+    version: v1.4.10
     docs_paths:
       - docs/toolhive/guides-registry
       - docs/toolhive/concepts/registry-criteria.mdx
diff --git a/docs/toolhive/guides-registry/audit-logging.mdx b/docs/toolhive/guides-registry/audit-logging.mdx
index 6eccf67a..3947c0b1 100644
--- a/docs/toolhive/guides-registry/audit-logging.mdx
+++ b/docs/toolhive/guides-registry/audit-logging.mdx
@@ -249,14 +249,9 @@ Because `AUDIT` is not a standard level name, some log aggregators may display
 it as `unknown`. To filter for audit events, match on `level = "AUDIT"` or
 `msg = "audit_event"` directly rather than relying on level detection.
 
-:::
-
-:::note[Known issue: `level` field may show as `INFO+2`]
-
-In some versions of the Registry Server, the `level` field is serialized as
-`"INFO+2"` rather than `"AUDIT"` (tracked in
-[#826](https://github.com/stacklok/toolhive-registry-server/issues/826)). If
-your logs show `"INFO+2"`, filter on `"INFO+2"` or `"audit_event"` instead.
+Registry Server v1.4.9 and earlier serialize the `level` field as `"INFO+2"`
+instead of `"AUDIT"`. When filtering logs from those versions, match on
+`level = "INFO+2"` or `msg = "audit_event"`.
 
 :::