Incident history
Sep 29, 2026
We have not seen any further errors after the fix was applied. All services are fully operational and stable. We will post an RCA on our status page after further investigation.
Sep 29, 2026 · 18:49 → 20:23Sep 28, 2026
Our engineers have confirmed that STT latency has fully recovered.
Sep 28, 2026 · 15:42 → 16:54We can confirm that the issue has been fixed and that the service is fully operational. Resolution time was 14:18 UTC We will post the RCA to the status page after the investigation.
Sep 28, 2026 · 13:57 → 14:39Sep 21, 2026
The elevated error rate has been resolved and we're following up internally to prevent future occurrences.
Sep 21, 2026 · 23:25 → 02:56Sep 19, 2026
The issue has been fully resolved and everything is functional again.
Sep 19, 2026 · 00:34 → 02:08Sep 10, 2026
Our engineers have confirmed full recovery of the Conversation Search functionality in the web UI and the API.
Sep 10, 2026 · 20:43 → 20:43Our engineers have deployed a fix that has fully restored Claude MCP functionality.
Sep 10, 2026 · 14:58 → 14:58Our engineers have confirmed full recovery of the Conversation Search functionality in the web UI and the API.
Sep 10, 2026 · 09:44 → 20:43Sep 9, 2026
Our engineers have deployed a fix that has fully restored Claude MCP functionality.
Sep 9, 2026 · 12:41 → 14:58Sep 7, 2026
Service has been fully restored to remaining affected areas. We will share further details on the cause.
Sep 7, 2026 · 07:20 → 07:20Service has been fully restored to remaining affected areas. We will share further details on the cause.
Sep 7, 2026 · 03:17 → 07:20Sep 4, 2026
After completing the monitoring stage, we have confirmed that STT latency has returned to baseline stability.
Sep 4, 2026 · 13:55 → 21:01The issue has been resolved, everything is back at normal.
Sep 4, 2026 · 12:12 → 12:12The issue has been resolved, everything is back at normal.
Sep 4, 2026 · 11:41 → 12:12