Incidents | TextQL Incidents reported on status page for TextQL https://status.textql.com/ https://d1lppblt9t2x15.cloudfront.net/logos/17890997deccdc2d037a0b0539ef7765.png Incidents | TextQL https://status.textql.com/ en Login recovered https://status.textql.com/ Sun, 12 Apr 2026 08:43:10 +0000 https://status.textql.com/#2ae6c2da9cc3332dc4caafdbb1448a4dd951c128dfd19fefa030f01173c99d48 Login recovered Login went down https://status.textql.com/ Sun, 12 Apr 2026 08:42:43 +0000 https://status.textql.com/#2ae6c2da9cc3332dc4caafdbb1448a4dd951c128dfd19fefa030f01173c99d48 Login went down Login recovered https://status.textql.com/ Sat, 11 Apr 2026 04:58:25 +0000 https://status.textql.com/#1ac8a31f8eaaa8eed817ed7d663d572aef6df93f9e1f7827c323c65e2e873c41 Login recovered Login went down https://status.textql.com/ Sat, 11 Apr 2026 04:57:41 +0000 https://status.textql.com/#1ac8a31f8eaaa8eed817ed7d663d572aef6df93f9e1f7827c323c65e2e873c41 Login went down Sandboxes degraded https://status.textql.com/incident/866496 Tue, 07 Apr 2026 18:57:00 -0000 https://status.textql.com/incident/866496#bc0120032eb50e502b8a993c225cca3190d7cf4fa2668c6bd8de4a9f71e91e62 The fix has been deployed. Dashboards degraded https://status.textql.com/incident/866453 Tue, 07 Apr 2026 17:36:17 -0000 https://status.textql.com/incident/866453#0f27eedb2cf814053b3e2de88868ae600659aad7d6380fd7b7bae76e45806980 Dashboards are fully operational. The degradation in start times has been resolved. Dashboards degraded https://status.textql.com/incident/866453 Tue, 07 Apr 2026 17:19:00 -0000 https://status.textql.com/incident/866453#6517c7de607580868b1a12590ac450cf381fc0b75fca5528262f7dc2ea687a19 Dashboards are seeing degradation in start times effecting some users. Sandboxes degraded https://status.textql.com/incident/866496 Tue, 07 Apr 2026 15:00:00 -0000 https://status.textql.com/incident/866496#219935a29a0325561a6b17a3f9f35b38b159ad282782cceae21e2e4d3994e22c Sandboxes created before 4:00 PM UDT are currently unavailable. New sandboxes / chats uneffected Threads and Playbooks degraded for some users https://status.textql.com/incident/862752 Wed, 01 Apr 2026 23:39:00 -0000 https://status.textql.com/incident/862752#4aace196261b79c089ced25c92eaaf4ed1c45778d1edf7ccd0e5b569c079b55d We have resolved the issues regarding threads in slack and playbook reports. Threads and Playbooks degraded for some users https://status.textql.com/incident/862752 Wed, 01 Apr 2026 21:56:00 -0000 https://status.textql.com/incident/862752#21e9936b131700a2ac05a9cd4504ea9a7496a083ce0ff6835781d0942649ad28 We are aware of issues impacting chat behavior, particularly for Slack threads and playbook reports. Sandbox degradation for some users https://status.textql.com/incident/856440 Tue, 24 Mar 2026 15:47:00 -0000 https://status.textql.com/incident/856440#75d5bdcaf0aa87070fe6bc75ce53a171d7eb5defa9d1821c24270dfa339538c3 A resolution has been shipped and tested. Sandbox degradation for some users https://status.textql.com/incident/856440 Tue, 24 Mar 2026 13:54:00 -0000 https://status.textql.com/incident/856440#7d21eb07ba357e8e8cd8a1320e6ac6f15acac725ab6e27cba2415e5879e034c5 We have observed some users have issues during initialization of sandboxes. A fix is in flight. Web App recovered https://status.textql.com/ Thu, 19 Mar 2026 04:26:16 +0000 https://status.textql.com/#887cdc3f520b07945c7334e9ed67fb68b6db4f417ffe61b26d3a19acdb5ce3e8 Web App recovered App Downtime https://status.textql.com/incident/852580 Thu, 19 Mar 2026 04:26:00 -0000 https://status.textql.com/incident/852580#0c48cfd2b86bca878ae755bd04a7514089f6d45de240cab6dd35b3c4f93cad08 Resolved Web App went down https://status.textql.com/ Thu, 19 Mar 2026 04:02:34 +0000 https://status.textql.com/#887cdc3f520b07945c7334e9ed67fb68b6db4f417ffe61b26d3a19acdb5ce3e8 Web App went down App Downtime https://status.textql.com/incident/852580 Thu, 19 Mar 2026 03:30:00 -0000 https://status.textql.com/incident/852580#b60df3eb13a9d498ffdbfff8456f68f966c684eee14272b6ff615dfa4fd94b05 App is currently down due to internal service errors. Will be back within 1 hour. Web App recovered https://status.textql.com/ Fri, 27 Feb 2026 07:41:37 +0000 https://status.textql.com/#69953805721d3082dc44a6f79e3ec986945624b2f600893f4b2d99a034200ec5 Web App recovered Web App went down https://status.textql.com/ Fri, 27 Feb 2026 07:41:22 +0000 https://status.textql.com/#69953805721d3082dc44a6f79e3ec986945624b2f600893f4b2d99a034200ec5 Web App went down Web App recovered https://status.textql.com/ Tue, 27 Jan 2026 15:49:15 +0000 https://status.textql.com/#4d99fd70c2f1213834d9c683a85fe36aa6c4718138f41799e35a3e37c4d6dc70 Web App recovered Web App went down https://status.textql.com/ Tue, 27 Jan 2026 15:48:34 +0000 https://status.textql.com/#4d99fd70c2f1213834d9c683a85fe36aa6c4718138f41799e35a3e37c4d6dc70 Web App went down Web App recovered https://status.textql.com/ Thu, 22 Jan 2026 23:57:21 +0000 https://status.textql.com/#71ad20b9f1bb07abcedfe44a6bfab27ce76136b273da538e8918dcf6577eba74 Web App recovered Web App went down https://status.textql.com/ Thu, 22 Jan 2026 23:56:37 +0000 https://status.textql.com/#71ad20b9f1bb07abcedfe44a6bfab27ce76136b273da538e8918dcf6577eba74 Web App went down