Incidents reported on status page for TextQL https://status.textql.com/ https://d1lppblt9t2x15.cloudfront.net/logos/17890997deccdc2d037a0b0539ef7765.png https://status.textql.com/ en https://status.textql.com/ Fri, 24 Jul 2026 11:14:37 +0000 https://status.textql.com/#ec1122a3016297379dcd7639a31114bf50838cf209646147cdea6c554e117c1b Login recovered https://status.textql.com/ Fri, 24 Jul 2026 11:11:45 +0000 https://status.textql.com/#5387f6186785ffe9b31acc300af88596213c347e2017bbc70aba09cbec9e1b17 Web App recovered https://status.textql.com/ Fri, 24 Jul 2026 10:57:29 +0000 https://status.textql.com/#5387f6186785ffe9b31acc300af88596213c347e2017bbc70aba09cbec9e1b17 Web App went down https://status.textql.com/ Fri, 24 Jul 2026 10:57:27 +0000 https://status.textql.com/#ec1122a3016297379dcd7639a31114bf50838cf209646147cdea6c554e117c1b Login went down https://status.textql.com/ Sun, 28 Jun 2026 13:36:46 +0000 https://status.textql.com/#dccda895d278f5a53af29d185e564738c28544e38ab950d01bc3fa098e3c20a0 Login recovered https://status.textql.com/ Sun, 28 Jun 2026 13:35:49 +0000 https://status.textql.com/#dccda895d278f5a53af29d185e564738c28544e38ab950d01bc3fa098e3c20a0 Login went down https://status.textql.com/ Thu, 18 Jun 2026 07:04:20 +0000 https://status.textql.com/#6a34546dbf227fd7d39379f4530b3879b509a5a0ebbd4618c7945e4c2bf41bdb Login recovered https://status.textql.com/ Thu, 18 Jun 2026 07:03:52 +0000 https://status.textql.com/#6a34546dbf227fd7d39379f4530b3879b509a5a0ebbd4618c7945e4c2bf41bdb Login went down https://status.textql.com/incident/927013 Wed, 17 Jun 2026 20:09:00 -0000 https://status.textql.com/incident/927013#8a430c18d8de7871f66f3e439ad9b88d6a56ef6c56eb07883e0c18768f22f656 Remediation is complete https://status.textql.com/incident/927013 Wed, 17 Jun 2026 19:29:00 -0000 https://status.textql.com/incident/927013#f139c02bfad49d6ef8e49fc3510980141522c774b441319a0ba7e8abca139444 Some users are seeing execution errors in threads due to "missing worker library backend in fsx deployment". We have identified the root cause and a remediation is in progress. https://status.textql.com/incident/922083 Fri, 12 Jun 2026 17:42:00 -0000 https://status.textql.com/incident/922083#f33e3b15e74610f3af1ac69a7d80fdd777befa3c4f48a6f84280b0220b98eb66 We have restored the application, users should no longer experience unexpected logout. https://status.textql.com/incident/922083 Fri, 12 Jun 2026 14:35:00 -0000 https://status.textql.com/incident/922083#382c8ef8148c9890399f68de7184b7c4c10e5c67e11414680614669ddb45c40f Some users are experiencing issues with unexpected logouts. We are investigating. https://status.textql.com/incident/918000 Mon, 08 Jun 2026 16:02:00 -0000 https://status.textql.com/incident/918000#e5ccb4b27d5a459f549e939db09646068e713785604f256e6c9b9138ccedc871 The fix has been deployed. https://status.textql.com/incident/918000 Mon, 08 Jun 2026 13:42:00 -0000 https://status.textql.com/incident/918000#94898ec15998856864925dfab30fcd8925749813d19ed637741f073de2af1eac We are investigating an issue where some users are experiencing degraded chat performance. Messages may appear as queued rather than sent. Our team is actively investigating and working on a resolution. We will provide updates as the situation develops. https://status.textql.com/incident/911433 Tue, 02 Jun 2026 21:46:00 -0000 https://status.textql.com/incident/911433#16e3995cf43b888e5efe25ba52bfa6137a65a6dc1508f95977e9e8e3fa67cea0 This has been resolved. https://status.textql.com/incident/911433 Tue, 02 Jun 2026 21:43:00 -0000 https://status.textql.com/incident/911433#cb8823e03b64436258040358ece5c32c78344df604201e79c6a709e0eb1f173d The issue has been identified and a fix is currently in flight. https://status.textql.com/incident/911433 Tue, 02 Jun 2026 21:40:00 -0000 https://status.textql.com/incident/911433#cd496344e737075236a403df67fb03624e7c579c68a3df1615441650fd0f9b79 Currently investigating login issues. https://status.textql.com/incident/908233 Fri, 29 May 2026 16:52:00 -0000 https://status.textql.com/incident/908233#6e7fa98a86595c2d7ebd6e4f1e3d0235c7a345abf22c9656f4ab2b308911f025 The sandbox degradation has been resolved. https://status.textql.com/incident/908233 Fri, 29 May 2026 13:50:00 -0000 https://status.textql.com/incident/908233#d09fd916e8e293d5bd017c2c9275c3cc97209d585dfb91451314b853edbce51b Some sandboxes are seeing degradation during startup. We have identified the issue and a fix is in flight. https://status.textql.com/ Sat, 23 May 2026 23:24:23 +0000 https://status.textql.com/#0bbb066e433c90fca08ba60033c1d5f1d561566feb26b72e94cde98dc468dede Login recovered https://status.textql.com/ Sat, 23 May 2026 23:23:54 +0000 https://status.textql.com/#0bbb066e433c90fca08ba60033c1d5f1d561566feb26b72e94cde98dc468dede Login went down https://status.textql.com/ Fri, 08 May 2026 00:48:10 +0000 https://status.textql.com/#5def64e337a3583f50536b69b8097447a901d8a0a0aac8a020a87a10511cbb0a Login recovered https://status.textql.com/ Fri, 08 May 2026 00:47:51 +0000 https://status.textql.com/#5def64e337a3583f50536b69b8097447a901d8a0a0aac8a020a87a10511cbb0a Login went down https://status.textql.com/incident/888437 Tue, 05 May 2026 20:41:00 -0000 https://status.textql.com/incident/888437#df2bcda813cdd3de5322480f63dd6c899a04519308f10c3d4d6771c5ff61b71a The web app has returned to normal state. https://status.textql.com/incident/888437 Tue, 05 May 2026 20:22:00 -0000 https://status.textql.com/incident/888437#9470ee21ee4698e7565083a9383fa2622691dd7b093a31d60f65ab22e427c1e1 Login into the application is currently unavailable. https://status.textql.com/incident/884356 Thu, 30 Apr 2026 15:15:00 -0000 https://status.textql.com/incident/884356#5891a179842238ef1b359538ac1051499f791c0dd7938df18a450b5e1dd48025 We have resolved the issue. https://status.textql.com/incident/884356 Thu, 30 Apr 2026 14:31:00 -0000 https://status.textql.com/incident/884356#b459a80b409986fd4930fa714478d580506ddbc7d926f77a7e93dff9ae780ad9 Some sandboxes are seeing high memory pressure. Larger dashboards and chats with complex Python may see issues. https://status.textql.com/incident/876545 Tue, 21 Apr 2026 19:00:00 -0000 https://status.textql.com/incident/876545#8679ff46d749be431b691792d449cbe33ca7b47908614f90fed6e45a6e6c13ff A fix has been tested and deployed. https://status.textql.com/incident/876545 Tue, 21 Apr 2026 17:17:00 -0000 https://status.textql.com/incident/876545#87cb581db24ce2d35fc63a563d164de132671014f82ad13f3a5d47a5f3e51d5c Degradation has resurface. Issue is identified https://status.textql.com/incident/876545 Tue, 21 Apr 2026 15:10:00 -0000 https://status.textql.com/incident/876545#63a902bc984d8f578812d09d2eb79157eb8ce4d272dca4ae253c2c600df0e929 The issue has been resolved. https://status.textql.com/incident/876545 Tue, 21 Apr 2026 13:29:00 -0000 https://status.textql.com/incident/876545#4e3ffe8e152498681e570e24af2b9237509b39e70bacc32134665027797d2ea5 Some users may experience timeouts when running queries. We have identified the cause and a fix is in progress. https://status.textql.com/incident/873100 Thu, 16 Apr 2026 14:53:00 -0000 https://status.textql.com/incident/873100#d67819866bf3ee7d5ddda102cb86d91139fbde00420d3d83d460ee4b38b550c5 Context is restored https://status.textql.com/incident/873100 Thu, 16 Apr 2026 13:50:00 -0000 https://status.textql.com/incident/873100#a23a953ff2c987bc2710fc1ab9a3c0f667ff60a5c3ff28969dea7e5d35ef3814 Context entries became invisible. We are restoring ASAP 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. 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. 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. 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 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. 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. 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. 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. https://status.textql.com/incident/852580 Thu, 19 Mar 2026 04:26:00 -0000 https://status.textql.com/incident/852580#0c48cfd2b86bca878ae755bd04a7514089f6d45de240cab6dd35b3c4f93cad08 Resolved 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.