diff --git a/cloud/docs/relay-reconnect-2026-09-findings.md b/cloud/docs/relay-reconnect-2026-09-findings.md
index 36c86244684..1d610d9784f 100644
--- a/cloud/docs/relay-reconnect-2026-09-findings.md
+++ b/cloud/docs/relay-reconnect-2026-09-findings.md
@@ -379,7 +379,8 @@ Fourth cascade 09:00:12–09:00:18Z: c23, c8, c16, c26, c22 (five cells, 11 cont
 all `5aedbca5`, exitCode 1, Node banner, pg-pool `client closed the connection` burst right before). Cloud
 SQL CPU 0.84 -> 0.78 in the preceding minutes, director concurrency 18–22 (idle), so this one fired
 *without* a database or director spike. Fleet had just recovered to 13,015. Cadence today: 01:31 (4),
-04:47 (5), 08:40 (10), 09:00 (5), 09:31 (2: c13, c23). The old image is now cascading roughly hourly regardless of load; the
+04:47 (5), 08:40 (10), 09:00 (5), 09:31 (c13, c23), 09:34 (c23 again, c14, c20, c9; c14/c20 crash-looping).
+Director concurrency pinned at 85 for 09:32–09:33; 503s 4,141 and 4,396 per minute. The old image is now cascading roughly hourly regardless of load; the
 only cell on a fixed image (c7) has 0 crashes in 2.5 h across all four.
 
 Director 500s: 4 in the 09:00 window, all 2.0 s latency on `/v1/assign` or `/v1/resolve` = pg-pool connect