Incidents and maintenance reported on status page for Ampersand https://status.withampersand.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/fa784bc02371f35a747149270323787d.png https://status.withampersand.ai/ en https://status.withampersand.ai/incident/1027957 Fri, 21 Aug 2026 21:02:00 -0000 https://status.withampersand.ai/incident/1027957#4b84c28faca2caaac2a60aceca67689917b42e056c50a2d35d0bf7af873a211f Incident Back-filled from our internal incident record before this status page existed; timestamps are the internal ones. 2026-08-21 21:02 UTC — Detected. Our liveness probe began timing out; the API writer database sat at 100% CPU. Root cause: the org-scoped health check ran an unbounded aggregate query against the primary database on every tick and became its heaviest statement. Capture ingest and Heimdall reads were slow or intermittently timing out for workspaces hosted by Ampersand. No data was lost. 2026-08-22 02:42 UTC — Fix 1 deployed: the health check now runs on the read replica with a strict statement timeout and a 60-second per-org cache. 2026-08-22 02:47 UTC — Probe latency back to normal (2.0s → 0.47s); alarm cleared. 2026-08-22 04:05 UTC — Fix 2 deployed: the expensive 7-day row count is now best-effort and never blocks the probe. Customer-deployed (BYOC) workspaces were not affected.