Incidents and maintenance reported on status page for Dharta https://status.dharta.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/270945c0993a45314b9ad088e454458a.png https://status.dharta.ai/ en https://status.dharta.ai/incident/993042 Sun, 02 Aug 2026 22:52:16 -0000 https://status.dharta.ai/incident/993042#3e3801a71f458b86ad8986437e0df69b9ef91f45ff563a8d7daf564356355886 Incident Resolved as of 22:39 UTC. karta.sh and the console are serving normally. We are adding image retention limits and a low-disk alarm to prevent a recurrence. https://status.dharta.ai/incident/993042 Sun, 02 Aug 2026 22:51:57 -0000 https://status.dharta.ai/incident/993042#0e2b4b50708c886772f69e487f2193a41844993d6c625f6a2535d310c2af5b31 Incident Between 22:24 and 22:39 UTC on 2 August, karta.sh and the control plane console returned 502 errors. The host disk filled up, which prevented the database from starting. Container images from previous deploys had accumulated on the host and were not being cleaned up. We reclaimed the disk space and the database restarted cleanly with no data loss. Service was restored at 22:39 UTC. Agent sessions on the data plane were not affected. https://status.dharta.ai/maintenance/977903 Sat, 25 Jul 2026 16:40:28 -0000 https://status.dharta.ai/incident/977903#0ee9e727f3698a09fa5c763999cba54510875b77530b5948e493b2271e6c74b2 Maintenance We are doubling the memory on the database that backs agent sessions, following the outage on 23 July. The database restarts as part of the change. Requests to api.karta.sh that need session data will fail for up to 10 minutes during the window. karta.sh and the control plane are unaffected. https://status.dharta.ai/incident/977899 Thu, 23 Jul 2026 07:35:00 -0000 https://status.dharta.ai/incident/977899#7a42681e973a5b14f3cf72ea3b7cd7b0b7c56d4ebe79804a3a1956e79707346d Incident Resolved. The database completed its restart and the API recovered. https://status.dharta.ai/incident/977899 Thu, 23 Jul 2026 07:35:00 -0000 https://status.dharta.ai/incident/977899#5beb5b9ea458f59f69c62b83914443f2ea2fdb590ac0c1be2cce7018fc4f6d41 Incident Between 07:18 and 07:35 UTC on 23 July, the database that stores agent session state ran out of memory and was restarted automatically. Requests to api.karta.sh that needed session data failed or timed out during that window. karta.sh and the control plane were unaffected. A change deployed at 05:12 UTC caused a background usage-accounting job to replay 24 hours of records on every five-minute cycle. That load drained the database's memory over roughly two hours until it restarted. A fix that bounds the job landed the same day. We have since added memory, CPU credit, and storage alarms on that database, and the API readiness check now verifies it can reach the session store, so this kind of failure surfaces directly instead of appearing as a brief unexplained timeout.