diff --git a/3.11/release-notes-api-changes311.md b/3.11/release-notes-api-changes311.md
index 13cf15c20a..c689a02318 100644
--- a/3.11/release-notes-api-changes311.md
+++ b/3.11/release-notes-api-changes311.md
@@ -129,6 +129,12 @@ Enterprise Edition:
   Like the existing `geojson` Analyzer, but with an additional `format` property
   that can be set to `"latLngDouble"` (default), `"latLngInt"`, or `"s2Point"`.
 
+#### Query API
+
+The [`GET /_api/query/current`](http/aql-query.html#returns-the-currently-running-aql-queries)
+and [`GET /_api/query/slow`](http/aql-query.html#returns-the-list-of-slow-aql-queries)
+endpoints include a new numeric `peakMemoryUsage` attribute.
+
 ### Endpoints moved
 
 
diff --git a/3.11/release-notes-new-features311.md b/3.11/release-notes-new-features311.md
index 15ad86c8ee..004f883190 100644
--- a/3.11/release-notes-new-features311.md
+++ b/3.11/release-notes-new-features311.md
@@ -88,6 +88,17 @@ example query, but you can also specify your preferred method explicitly.
 
 See the [`COLLECT` options](aql/operations-collect.html#method) for details.
 
+### Extended peak memory usage reporting
+
+The peak memory usage of AQL queries is now also reported for running queries
+and slow queries.
+
+In the web interface, you can find the **Peak memory usage** column in the
+**QUERIES** section, in the **Running Queries** and **Slow Query History** tabs.
+
+In the JavaScript and HTTP APIs, the value is reported as `peakMemoryUsage`.
+See [API Changes in ArangoDB 3.11](release-notes-api-changes311.html#query-api).
+
 ## Server options
 
 ### Verify `.sst` files