Incidents reported on status page for Langdock https://status.langdock.com/ https://d1lppblt9t2x15.cloudfront.net/logos/4ff743a4defdc7a8a024eca9d936d8af.png https://status.langdock.com/ en https://status.langdock.com/ Wed, 15 Apr 2026 02:37:19 +0000 https://status.langdock.com/#24a4b303a009aae65c292993151324737eed5c1be537b68bbe2c2e5e80ef0828 Workflows Runtime recovered https://status.langdock.com/ Wed, 15 Apr 2026 02:34:57 +0000 https://status.langdock.com/#24a4b303a009aae65c292993151324737eed5c1be537b68bbe2c2e5e80ef0828 Workflows Runtime went down https://status.langdock.com/incident/871149 Tue, 14 Apr 2026 06:26:00 -0000 https://status.langdock.com/incident/871149#4e3bd1ac629810268c027449addfb4001a1c26ddc0433e7e1fe0caa516fa15b4 We have identified the issue and released a fix. This issue is resolved. https://status.langdock.com/ Tue, 14 Apr 2026 03:32:32 +0000 https://status.langdock.com/#1b864b6c971126f8dc2de1ae8febeb607feae963071098cacba1d5969e15d29d Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Apr 2026 03:10:53 +0000 https://status.langdock.com/#1b864b6c971126f8dc2de1ae8febeb607feae963071098cacba1d5969e15d29d Workflows Runtime went down https://status.langdock.com/ Tue, 14 Apr 2026 02:58:29 +0000 https://status.langdock.com/#2e5e73a0dbdca6e47d521a1a6be46a8fdac470852308fad0712b3845fc95697e Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Apr 2026 02:56:19 +0000 https://status.langdock.com/#2e5e73a0dbdca6e47d521a1a6be46a8fdac470852308fad0712b3845fc95697e Workflows Runtime went down https://status.langdock.com/ Tue, 14 Apr 2026 02:36:18 +0000 https://status.langdock.com/#a0c0310e14f3a9d4574741654090bb750e83e9f1ace187481e9b4a1d00e68426 Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Apr 2026 02:34:53 +0000 https://status.langdock.com/#a0c0310e14f3a9d4574741654090bb750e83e9f1ace187481e9b4a1d00e68426 Workflows Runtime went down https://status.langdock.com/ Tue, 14 Apr 2026 01:11:51 +0000 https://status.langdock.com/#10e140c29c6df1536048fbbbff02b0439122daac3f907d573afb779831a2cb99 Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Apr 2026 01:04:19 +0000 https://status.langdock.com/#10e140c29c6df1536048fbbbff02b0439122daac3f907d573afb779831a2cb99 Workflows Runtime went down https://status.langdock.com/incident/871149 Mon, 13 Apr 2026 18:15:00 -0000 https://status.langdock.com/incident/871149#2ad48c4febb7f0c00c6bf8a56003dfd27c0018c56c9c75b42bc1470d8d4d6640 We are investigating a high error rate across Workflow runs. https://status.langdock.com/ Thu, 09 Apr 2026 08:23:01 +0000 https://status.langdock.com/#18c1225757340cb2690cc007ae824d7a36dea7272ed0e278e667d3fdc2c02a52 Workflows Runtime recovered https://status.langdock.com/ Thu, 09 Apr 2026 07:56:55 +0000 https://status.langdock.com/#18c1225757340cb2690cc007ae824d7a36dea7272ed0e278e667d3fdc2c02a52 Workflows Runtime went down https://status.langdock.com/ Thu, 09 Apr 2026 00:06:04 +0000 https://status.langdock.com/#d134599ad5ddead1944d93b23c386bdd8b7a074d9831265eeac9ef2ebb7dad1f Workflows Runtime recovered https://status.langdock.com/ Thu, 09 Apr 2026 00:05:30 +0000 https://status.langdock.com/#d134599ad5ddead1944d93b23c386bdd8b7a074d9831265eeac9ef2ebb7dad1f Workflows Runtime went down https://status.langdock.com/ Wed, 08 Apr 2026 14:07:51 +0000 https://status.langdock.com/#39aef236a7d9003c51e40a52fc4dfc887209e7ec67f10161de3247996d61bdbf api.langdock.com recovered https://status.langdock.com/ Wed, 08 Apr 2026 14:05:09 +0000 https://status.langdock.com/#39aef236a7d9003c51e40a52fc4dfc887209e7ec67f10161de3247996d61bdbf api.langdock.com went down https://status.langdock.com/ Wed, 08 Apr 2026 08:16:11 +0000 https://status.langdock.com/#aa8863aa7282f6de62fc4de320e2d81815047c607a4867a33b44c5e2c18ed659 Workflows Runtime recovered https://status.langdock.com/ Wed, 08 Apr 2026 07:49:33 +0000 https://status.langdock.com/#aa8863aa7282f6de62fc4de320e2d81815047c607a4867a33b44c5e2c18ed659 Workflows Runtime went down https://status.langdock.com/ Tue, 07 Apr 2026 01:10:14 +0000 https://status.langdock.com/#6f9232be4dc46fad67436555df86a8a2669011d382034e3eeda468fe54c35562 Workflows Runtime recovered https://status.langdock.com/ Tue, 07 Apr 2026 01:08:28 +0000 https://status.langdock.com/#6f9232be4dc46fad67436555df86a8a2669011d382034e3eeda468fe54c35562 Workflows Runtime went down https://status.langdock.com/ Sat, 04 Apr 2026 00:05:18 +0000 https://status.langdock.com/#d0ca6d8324fa07b29e0688cdf7f6d5a9f4f23329543d802a5a14f443578ad8af Workflows Runtime recovered https://status.langdock.com/ Sat, 04 Apr 2026 00:04:20 +0000 https://status.langdock.com/#d0ca6d8324fa07b29e0688cdf7f6d5a9f4f23329543d802a5a14f443578ad8af Workflows Runtime went down https://status.langdock.com/ Fri, 03 Apr 2026 22:43:04 +0000 https://status.langdock.com/#3780bb7f0cf77fa972a39fa06dfabcd76ee212bd19edb9157aa00341c32d9491 Workflows Runtime recovered https://status.langdock.com/ Fri, 03 Apr 2026 22:42:12 +0000 https://status.langdock.com/#3780bb7f0cf77fa972a39fa06dfabcd76ee212bd19edb9157aa00341c32d9491 Workflows Runtime went down https://status.langdock.com/ Fri, 03 Apr 2026 22:31:51 +0000 https://status.langdock.com/#b3ef073c1fd119d004bc2ef002b1dc4b8cd9bfb839c40701385658f2d4e7ea35 Workflows Runtime recovered https://status.langdock.com/ Fri, 03 Apr 2026 22:30:14 +0000 https://status.langdock.com/#b3ef073c1fd119d004bc2ef002b1dc4b8cd9bfb839c40701385658f2d4e7ea35 Workflows Runtime went down https://status.langdock.com/ Thu, 02 Apr 2026 18:15:43 +0000 https://status.langdock.com/#fb3a393a6283ec6095b382be7bb7be17e11eeb3334a3ef8700945f701273e2ce Workflows Runtime recovered https://status.langdock.com/ Thu, 02 Apr 2026 17:49:57 +0000 https://status.langdock.com/#fb3a393a6283ec6095b382be7bb7be17e11eeb3334a3ef8700945f701273e2ce Workflows Runtime went down https://status.langdock.com/ Wed, 01 Apr 2026 22:41:04 +0000 https://status.langdock.com/#b7534e34d387a7b48ad23ed8941bfe4b89a198d06f0823b13da5c4baa7686a67 Workflows Runtime recovered https://status.langdock.com/ Wed, 01 Apr 2026 22:13:10 +0000 https://status.langdock.com/#b7534e34d387a7b48ad23ed8941bfe4b89a198d06f0823b13da5c4baa7686a67 Workflows Runtime went down https://status.langdock.com/ Wed, 01 Apr 2026 21:14:37 +0000 https://status.langdock.com/#0f129961e97ede91b636559acb609c9915ef0671e48f06c33f31b986c72e9510 Workflows Runtime recovered https://status.langdock.com/ Wed, 01 Apr 2026 20:46:38 +0000 https://status.langdock.com/#0f129961e97ede91b636559acb609c9915ef0671e48f06c33f31b986c72e9510 Workflows Runtime went down https://status.langdock.com/ Tue, 31 Mar 2026 19:53:08 +0000 https://status.langdock.com/#6fe18b5d40b2bc0684a8fdb21a4acef6f851dd82a90fd4c1a3e8d12d505fd0af api.langdock.com recovered https://status.langdock.com/ Tue, 31 Mar 2026 19:41:13 +0000 https://status.langdock.com/#6fe18b5d40b2bc0684a8fdb21a4acef6f851dd82a90fd4c1a3e8d12d505fd0af api.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 21:18:52 +0000 https://status.langdock.com/#648859fe4ab31f09394fec6d83efcf1cf94d48cbeb37c11d82a8fff96076e4eb app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 21:12:16 +0000 https://status.langdock.com/#648859fe4ab31f09394fec6d83efcf1cf94d48cbeb37c11d82a8fff96076e4eb app.langdock.com went down https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 16:45:00 -0000 https://status.langdock.com/incident/860648#973bb097079d466803bef143caff38457c6a0ac0877440b3ca7005a33a452f24 ## Post-Mortem: Service Disruption – March 30, 2026 Duration: 8:00 AM – 4:36 PM CEST Severity: Major Affected: app.langdock.com Status: Resolved ### What Happened On March 30, 2026, Langdock experienced a major service disruption caused by a platform-level degradation on Azure Container Apps (ACA). Containers that normally start in under 2 minutes took over 15 minutes during the incident, preventing our autoscaler from bringing new capacity online and leading to a full platform outage from approximately 11:30 AM CEST. ### Timeline (CEST) 8:00 AM — Performance degradation detected 9:15 AM — Issue identified; hotfix deployed 9:43 AM — Performance stabilised, partial recovery 9:55 AM — Downstream issues discovered; investigation continues 10:45 AM — Core platform restored; workflows & file uploads still affected 11:30 AM — Full platform outage begins due to cascading downstream effects from increased startup time of ACA. 12:11 PM — Platform taken fully offline for controlled reboot 3:34 PM — Platform restored and accepting traffic 4:36 PM — Workflows and file uploads fully restored 4:37 PM — Incident fully resolved ### Root Cause Azure Container Apps experienced a platform-level degradation affecting container startup times. The same container image started in under 30 seconds on AKS, confirming the issue was with ACA and not our application. ### Resolution & Next Steps We relaxed startup probes, raised the minimum container count, and temporarily disabled readiness/liveness probes to restore service. We are now implementing improved failover paths, improved startup monitoring, and better baseline capacity provisioning to prevent a recurrence. We sincerely apologize for the disruption. Please reach out to support@langdock.com with any questions. https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 15:32:00 -0000 https://status.langdock.com/incident/860648#411f456f4ac01ba89fefff7d713fcae360f02042e1ac5eaf49d60a4a0d01be9b We will follow up with a post mortem on this incident here. Thank you for your patience today! https://status.langdock.com/incident/860878 Mon, 30 Mar 2026 14:36:00 -0000 https://status.langdock.com/incident/860878#6352758450c3783eda15191f95f382516597f78f30c062fbb614ff81d99be939 The backlog has been processed. File uploads and workflows are running normally again. https://status.langdock.com/ Mon, 30 Mar 2026 14:27:52 +0000 https://status.langdock.com/#17deb72e9c34c0a041e893895a0b9ab120e40434e69a4f14ffd26d17297091fb Workflows Runtime recovered https://status.langdock.com/incident/860878 Mon, 30 Mar 2026 14:05:00 -0000 https://status.langdock.com/incident/860878#74777c2cf6acca00b7adc25d1852a893f85b870a7fcbe5faccd9cbc26dc6bbe0 We expect the backlog to clear in the next 20min. https://status.langdock.com/ Mon, 30 Mar 2026 14:04:15 +0000 https://status.langdock.com/#17deb72e9c34c0a041e893895a0b9ab120e40434e69a4f14ffd26d17297091fb Workflows Runtime went down https://status.langdock.com/ Mon, 30 Mar 2026 13:58:41 +0000 https://status.langdock.com/#f9d2d6226db2b150c864bb091fbd982f151020140df122e9517bfa7c5d565855 Workflows Runtime recovered https://status.langdock.com/incident/860878 Mon, 30 Mar 2026 13:51:00 -0000 https://status.langdock.com/incident/860878#c3f64f19c3c511af63dfcb7cab841b78e51dee5ca30deee9786924b52c41a151 Our workflow execution and file processing services are currently under a lot of load due to the incident earlier in the day. We expect the execution backlog to clear over the next hours. https://status.langdock.com/ Mon, 30 Mar 2026 13:45:48 +0000 https://status.langdock.com/#f9d2d6226db2b150c864bb091fbd982f151020140df122e9517bfa7c5d565855 Workflows Runtime went down https://status.langdock.com/ Mon, 30 Mar 2026 13:33:57 +0000 https://status.langdock.com/#c3c9a9802c52ba4765274aea4c6bd6a24b72314b2d66bbb40eef86f9b1fdc603 app.langdock.com recovered https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 13:32:00 -0000 https://status.langdock.com/incident/860648#7b0080501394200500c2185359b34ebc5e8560a38e255c3a86ad4df844a1fabb We have completed the system reboot and the platform is accepting traffic again. We continue to monitor the platform status very closely. https://status.langdock.com/ Mon, 30 Mar 2026 13:23:24 +0000 https://status.langdock.com/#c633132346cc946d0fa21efe2d4d59fbfac9337107d2bc191bb21ee2bba62367 api.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 13:09:08 +0000 https://status.langdock.com/#c633132346cc946d0fa21efe2d4d59fbfac9337107d2bc191bb21ee2bba62367 api.langdock.com went down https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 12:43:00 -0000 https://status.langdock.com/incident/860648#7095d2c8daea6998bb4cf51423f0d0dfabe5b35e2f11cf6166e313fef99bbe73 We are making progress with the full system reboot. Thanks for your patience! https://status.langdock.com/ Mon, 30 Mar 2026 12:34:12 +0000 https://status.langdock.com/#80e98ed0377bf8f6772834175144a8fa05bdf83cec485afd6aa13b07559fea37 Workflows Runtime recovered https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 12:12:00 -0000 https://status.langdock.com/incident/860648#79fd1899c64a6054de846bb07e4d126f55b0bd54b704afdee8a7aad294da7d2e We continue with the full system reboot. Thanks for your patience! https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 11:46:00 -0000 https://status.langdock.com/incident/860648#2472fe81845359e9db2cb9d01fb2d2c0f8576ba311578f3190db4ccb5cfb5b73 We continue with the full system reboot. Thanks for your patience! https://status.langdock.com/ Mon, 30 Mar 2026 11:43:08 +0000 https://status.langdock.com/#083bed121396a7642f402bd3747f7efc688a03d309bc173b4a74a3039502634f api.langdock.com recovered https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 11:31:00 -0000 https://status.langdock.com/incident/860648#30033c7df6e3abe34d6cd9c428eed8fcd5a82b81b69f163d8f8c5f5525dd2e39 We continue with the full system reboot. https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 11:01:00 -0000 https://status.langdock.com/incident/860648#5f0da6158d4e661215a9887aee03057cac315ea8860b9907d16811e389945445 We continue with the full system reboot. https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 10:37:00 -0000 https://status.langdock.com/incident/860648#d347e1944a7f932a8aa9c767f516c08dab2d2cba99d2276e6bd0f1df20436be8 We continue to reboot the system. https://status.langdock.com/ Mon, 30 Mar 2026 10:13:09 +0000 https://status.langdock.com/#083bed121396a7642f402bd3747f7efc688a03d309bc173b4a74a3039502634f api.langdock.com went down https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 10:11:00 -0000 https://status.langdock.com/incident/860648#10159693ff7f4491ed2bc553b3d92d2e14fca4214d1d65f9323d2c7ea323618c The platform is currently completely shut down as we attempt a full system reboot. https://status.langdock.com/ Mon, 30 Mar 2026 10:03:02 +0000 https://status.langdock.com/#c3c9a9802c52ba4765274aea4c6bd6a24b72314b2d66bbb40eef86f9b1fdc603 app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 09:50:28 +0000 https://status.langdock.com/#76be116c9df84f2cec4ad6024227de3a57448e8d223038d306180190525900eb app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 09:49:40 +0000 https://status.langdock.com/#76be116c9df84f2cec4ad6024227de3a57448e8d223038d306180190525900eb app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 09:48:03 +0000 https://status.langdock.com/#de5ecf2300e22fe0231fe9cffc34b7c259ad6b68037b8a356f8b06a824509c4d app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 09:44:45 +0000 https://status.langdock.com/#de5ecf2300e22fe0231fe9cffc34b7c259ad6b68037b8a356f8b06a824509c4d app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 09:43:29 +0000 https://status.langdock.com/#f559b23a6a4c544ee74e3c208e0c8d5eab3daadc6a37d21c303bbd7c78c34c6a app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 09:40:08 +0000 https://status.langdock.com/#f559b23a6a4c544ee74e3c208e0c8d5eab3daadc6a37d21c303bbd7c78c34c6a app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 09:38:31 +0000 https://status.langdock.com/#ddd368a892a1b18702b331576ded3bffc8ce36b1e478e3f1a3a6d031a9fe82ac app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 09:37:33 +0000 https://status.langdock.com/#ddd368a892a1b18702b331576ded3bffc8ce36b1e478e3f1a3a6d031a9fe82ac app.langdock.com went down https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 09:37:00 -0000 https://status.langdock.com/incident/860648#d8cb7962abf8fd3d8b7b56e06b3801fe56216d37bc4f0b904f62faf797ccd2c3 We continue to investigate degraded performance and high error rates across our services. https://status.langdock.com/ Mon, 30 Mar 2026 09:34:25 +0000 https://status.langdock.com/#a2e305500e66da009c6fae2b088c7c47a60a5cfd8ec3a484ad10112062aa5959 app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 09:33:28 +0000 https://status.langdock.com/#a2e305500e66da009c6fae2b088c7c47a60a5cfd8ec3a484ad10112062aa5959 app.langdock.com went down https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 08:45:00 -0000 https://status.langdock.com/incident/860648#40d1e306236cc3f8ff212ff59841a0d3195aed5e09701f22aa02df7aec64a73a We have stabilised the core platform. Most parts of the platform are available again, we are now working to bring workflow executions and file uploads back. https://status.langdock.com/ Mon, 30 Mar 2026 08:32:30 +0000 https://status.langdock.com/#60a33816d596a67b21a93ce7293818cb4eda29cc3586767bde1ff547d768a8df app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 08:24:25 +0000 https://status.langdock.com/#60a33816d596a67b21a93ce7293818cb4eda29cc3586767bde1ff547d768a8df app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 08:22:38 +0000 https://status.langdock.com/#80e98ed0377bf8f6772834175144a8fa05bdf83cec485afd6aa13b07559fea37 Workflows Runtime went down https://status.langdock.com/ Mon, 30 Mar 2026 08:22:06 +0000 https://status.langdock.com/#8019e51fae2695ae7483980298b66d5b040b6512e34308f5b3c31a10ae4d156b app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 08:20:39 +0000 https://status.langdock.com/#8019e51fae2695ae7483980298b66d5b040b6512e34308f5b3c31a10ae4d156b app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 08:19:26 +0000 https://status.langdock.com/#3c2ab2676180ecfd6a839c3f30fb39c3340dbdd17f44a42098fc298ba19e16a0 app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 08:18:39 +0000 https://status.langdock.com/#3c2ab2676180ecfd6a839c3f30fb39c3340dbdd17f44a42098fc298ba19e16a0 app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 08:17:04 +0000 https://status.langdock.com/#7b752971d00decc4f271723fbfa6f07776f90f32fcc6cf0bfd5fea180462b885 app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 08:15:08 +0000 https://status.langdock.com/#7b752971d00decc4f271723fbfa6f07776f90f32fcc6cf0bfd5fea180462b885 app.langdock.com went down https://status.langdock.com/ Mon, 30 Mar 2026 08:13:59 +0000 https://status.langdock.com/#fc2e4a0bafd096656030523291147f913e4272a997b8ff710587cc79fc8cf5cd app.langdock.com recovered https://status.langdock.com/ Mon, 30 Mar 2026 08:11:15 +0000 https://status.langdock.com/#fc2e4a0bafd096656030523291147f913e4272a997b8ff710587cc79fc8cf5cd app.langdock.com went down https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 07:55:00 -0000 https://status.langdock.com/incident/860648#460d62ea9b66367c5aee60cb5e19df7c84ef79dc1da0ad75950feb8ce4687313 We stabilised parts of the platform but discovered downstream issues with our LLM services. We continue to investigate. https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 07:43:00 -0000 https://status.langdock.com/incident/860648#dcf5e41eb7d817d3d70e288ee110e44c4577676480781e5f0d6306250d040e29 We have deployed a fix. The performance is back to normal levels. https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 07:15:00 -0000 https://status.langdock.com/incident/860648#58967a2e5d3098ca2e3a7a713f5be58bdbb261dcf085a3c5859448487cd646c2 We have identified the underlying issue and are deploying a fix. https://status.langdock.com/incident/860648 Mon, 30 Mar 2026 06:00:00 -0000 https://status.langdock.com/incident/860648#3f441969a41b34991303db1a8e93230fc315ea521f19ec5fb1f8fe13369d34ac Performance of the platform is currently degraded. https://status.langdock.com/ Sun, 29 Mar 2026 09:12:20 +0000 https://status.langdock.com/#29755312c3792dc61e05167df9b7b8d5beb420a62397a4fb10c01888205d2cd4 Workflows Runtime recovered https://status.langdock.com/ Sun, 29 Mar 2026 09:00:41 +0000 https://status.langdock.com/#29755312c3792dc61e05167df9b7b8d5beb420a62397a4fb10c01888205d2cd4 Workflows Runtime went down https://status.langdock.com/ Thu, 26 Mar 2026 19:15:12 +0000 https://status.langdock.com/#955c9678734d5cd68ebb470a26099df528ddbe7cd7c3c3a5399c90f3064d8ab4 api.langdock.com recovered https://status.langdock.com/ Thu, 26 Mar 2026 19:07:08 +0000 https://status.langdock.com/#955c9678734d5cd68ebb470a26099df528ddbe7cd7c3c3a5399c90f3064d8ab4 api.langdock.com went down https://status.langdock.com/ Wed, 25 Mar 2026 09:51:10 +0000 https://status.langdock.com/#a7a10f1e8ca6497416b1bfa7545a1fee2d1f5b8fc45cf6d5f829be9dfb6e1347 api.langdock.com recovered https://status.langdock.com/ Wed, 25 Mar 2026 09:49:10 +0000 https://status.langdock.com/#a7a10f1e8ca6497416b1bfa7545a1fee2d1f5b8fc45cf6d5f829be9dfb6e1347 api.langdock.com went down https://status.langdock.com/ Tue, 24 Mar 2026 16:57:12 +0000 https://status.langdock.com/#11c148c8419c9fc0aec04f62122c4dfefccd6f1e45c6a3d5f37e495cbc354ce1 api.langdock.com recovered https://status.langdock.com/ Tue, 24 Mar 2026 16:55:09 +0000 https://status.langdock.com/#11c148c8419c9fc0aec04f62122c4dfefccd6f1e45c6a3d5f37e495cbc354ce1 api.langdock.com went down https://status.langdock.com/ Tue, 24 Mar 2026 01:17:42 +0000 https://status.langdock.com/#02abd3af3e76efc79adb6c166956e8fe89b81891fe456abd23cb6c8ddab2fa8d Workflows Runtime recovered https://status.langdock.com/ Tue, 24 Mar 2026 01:14:55 +0000 https://status.langdock.com/#02abd3af3e76efc79adb6c166956e8fe89b81891fe456abd23cb6c8ddab2fa8d Workflows Runtime went down https://status.langdock.com/incident/852311 Wed, 18 Mar 2026 19:16:00 -0000 https://status.langdock.com/incident/852311#e1224346bba5f398518940f3e46689ef4bb2a82d31455942cf441e65d73df3fd We have identified the root cause of the issue and released a fix. https://status.langdock.com/incident/852311 Wed, 18 Mar 2026 17:58:00 -0000 https://status.langdock.com/incident/852311#46adc5b87c34951c3627a5ebf80a9c94d4e481291aa58904abda5e36b8b7a294 We are aware of an issue where the web search in chat and workflows is not producing results. We are currently working on a fix for this issue. https://status.langdock.com/ Wed, 18 Mar 2026 08:24:28 +0000 https://status.langdock.com/#5b13217a33543defa070137d3b2d8edbd9904cfabbfff288d01543c5fecb3890 app.langdock.com recovered https://status.langdock.com/ Wed, 18 Mar 2026 08:22:45 +0000 https://status.langdock.com/#5b13217a33543defa070137d3b2d8edbd9904cfabbfff288d01543c5fecb3890 app.langdock.com went down https://status.langdock.com/ Sun, 15 Mar 2026 18:32:27 +0000 https://status.langdock.com/#71c66a199c40ce70282a7da110ff87ea54e087c3aa0b51eab4f832f9507790cb app.langdock.com recovered https://status.langdock.com/ Sun, 15 Mar 2026 18:30:27 +0000 https://status.langdock.com/#71c66a199c40ce70282a7da110ff87ea54e087c3aa0b51eab4f832f9507790cb app.langdock.com went down https://status.langdock.com/ Sun, 15 Mar 2026 18:24:37 +0000 https://status.langdock.com/#5f0dc066816c8380d6b262368a9575528f0a1e51aa1631434390f0a413918e35 app.langdock.com recovered https://status.langdock.com/ Sun, 15 Mar 2026 18:22:17 +0000 https://status.langdock.com/#5f0dc066816c8380d6b262368a9575528f0a1e51aa1631434390f0a413918e35 app.langdock.com went down https://status.langdock.com/ Sun, 15 Mar 2026 13:47:31 +0000 https://status.langdock.com/#6681b24e7c9e3c36754707e58a95eaaf57b73d22e4b85823dc4a0cf89209c4a4 app.langdock.com recovered https://status.langdock.com/ Sun, 15 Mar 2026 13:43:21 +0000 https://status.langdock.com/#6681b24e7c9e3c36754707e58a95eaaf57b73d22e4b85823dc4a0cf89209c4a4 app.langdock.com went down https://status.langdock.com/incident/849761 Sun, 15 Mar 2026 13:25:24 -0000 https://status.langdock.com/incident/849761#4e64ecea771bace400e08a3004240dcac28fcfe466e776da0dad2bfc4e91b8f8 We are updating the Langdock system infrastructure and the systems availability might be impacted for a few minutes. https://status.langdock.com/incident/844064 Sun, 08 Mar 2026 03:34:00 -0000 https://status.langdock.com/incident/844064#74a71da3a9a4ed353ebb63bee9f3413414d3b699c3f56aa342e0e875bd359815 We have identified the root cause and fixed the issue. Langdock is available again for all users. We will continue to monitor the situation. https://status.langdock.com/ Sun, 08 Mar 2026 03:33:01 +0000 https://status.langdock.com/#d2248ef39df2a51691cd920119b712cfbdc0f3e9f80c196cd86c4869827012fd app.langdock.com recovered https://status.langdock.com/incident/844064 Sun, 08 Mar 2026 03:29:00 -0000 https://status.langdock.com/incident/844064#c7514263b0593afed9ffd3ed37cd87d3ebf870dfc5fda19cd24e7bb08fcf853c We're currently experiencing issues and Langdock is unavailable for all users. We're investigating and will keep you updated. https://status.langdock.com/ Sun, 08 Mar 2026 03:27:29 +0000 https://status.langdock.com/#d2248ef39df2a51691cd920119b712cfbdc0f3e9f80c196cd86c4869827012fd app.langdock.com went down https://status.langdock.com/incident/833794 Thu, 26 Feb 2026 06:34:00 -0000 https://status.langdock.com/incident/833794#06134a89209728927c560364e74a40dd9c4fed2c72528cd842fca4eb4608b51c We have identified the root cause and fixed the issue. Langdock is available again for all users. We will continue to monitor the situation. https://status.langdock.com/ Thu, 26 Feb 2026 06:31:14 +0000 https://status.langdock.com/#9cd3fc010425e9f816e93e5bde67e2acddf5f0d495cbb4af7636c94dea24961f api.langdock.com recovered https://status.langdock.com/ Thu, 26 Feb 2026 06:29:33 +0000 https://status.langdock.com/#7f6652cadb453d2d817837d1e8dd223998e4d38fcd0195cc2a699b0e05a3f473 Workflows Runtime recovered https://status.langdock.com/ Thu, 26 Feb 2026 06:29:04 +0000 https://status.langdock.com/#10d598a838230af4bd96d1e30908e1fe0d42ac8332f74cf09e618a8c294bc9b0 app.langdock.com recovered https://status.langdock.com/ Thu, 26 Feb 2026 06:18:16 +0000 https://status.langdock.com/#7f6652cadb453d2d817837d1e8dd223998e4d38fcd0195cc2a699b0e05a3f473 Workflows Runtime went down https://status.langdock.com/ Thu, 26 Feb 2026 06:17:12 +0000 https://status.langdock.com/#9cd3fc010425e9f816e93e5bde67e2acddf5f0d495cbb4af7636c94dea24961f api.langdock.com went down https://status.langdock.com/incident/833794 Thu, 26 Feb 2026 06:16:00 -0000 https://status.langdock.com/incident/833794#6b33d70c2a2c468b37148ccf6509d83da8c3408e0412a73196ad9b4248c4a4aa We're currently experiencing issues and Langdock is unavailable for all users. We're investigating and will keep you updated. https://status.langdock.com/ Thu, 26 Feb 2026 06:15:12 +0000 https://status.langdock.com/#10d598a838230af4bd96d1e30908e1fe0d42ac8332f74cf09e618a8c294bc9b0 app.langdock.com went down https://status.langdock.com/ Mon, 23 Feb 2026 10:57:03 +0000 https://status.langdock.com/#d1f01c6c964d5a114db6dc1041f807f19b7b1d6cee0b841b3291260e24adf187 app.langdock.com recovered https://status.langdock.com/ Mon, 23 Feb 2026 10:53:45 +0000 https://status.langdock.com/#d1f01c6c964d5a114db6dc1041f807f19b7b1d6cee0b841b3291260e24adf187 app.langdock.com went down https://status.langdock.com/ Fri, 20 Feb 2026 09:29:11 +0000 https://status.langdock.com/#e73044b967828ebae35431861d80dc8ab354a4ef2ee3029a72a5b0f97089297d app.langdock.com recovered https://status.langdock.com/ Fri, 20 Feb 2026 09:25:45 +0000 https://status.langdock.com/#e73044b967828ebae35431861d80dc8ab354a4ef2ee3029a72a5b0f97089297d app.langdock.com went down https://status.langdock.com/incident/826330 Mon, 16 Feb 2026 07:51:00 -0000 https://status.langdock.com/incident/826330#f0851fa8f88595046902e5f7e90d93e4ac29ee5ff22750134adc30924d07056e We have identified the root cause and restored the normal login flow. https://status.langdock.com/incident/826330 Sun, 15 Feb 2026 19:15:00 -0000 https://status.langdock.com/incident/826330#6613755c7f475ddfd29fbef7919c2f74cc3f90a580d1e311770cabc18486db38 At the moment login is only possible via Microsoft. We are working on restoring the usual login and will update as we have more information. https://status.langdock.com/ Fri, 13 Feb 2026 06:00:32 +0000 https://status.langdock.com/#7af04d18a73c198973c230f2b1156864b5d3846606cb5bad5eec530106fe7608 Workflows Runtime recovered https://status.langdock.com/ Fri, 13 Feb 2026 05:57:47 +0000 https://status.langdock.com/#7af04d18a73c198973c230f2b1156864b5d3846606cb5bad5eec530106fe7608 Workflows Runtime went down https://status.langdock.com/incident/823571 Wed, 11 Feb 2026 21:30:00 -0000 https://status.langdock.com/incident/823571#b2ffceaed4f8658c37c9efe7d7390531e0b6cae90fc7b1f9c959a96220c5571f We are performing an infrastructure upgrade and the performance of the application might be impacted for some minutes between 10:30pm and 11pm CET on February 11th 2026. https://status.langdock.com/ Thu, 05 Feb 2026 10:21:14 +0000 https://status.langdock.com/#322f9a8b73fc7c31675a2937ce509838114f274258f891cedd1cd31d0971c92f app.langdock.com recovered https://status.langdock.com/ Thu, 05 Feb 2026 10:18:46 +0000 https://status.langdock.com/#322f9a8b73fc7c31675a2937ce509838114f274258f891cedd1cd31d0971c92f app.langdock.com went down https://status.langdock.com/incident/816724 Mon, 02 Feb 2026 07:51:00 -0000 https://status.langdock.com/incident/816724#c7e883e304b2e4736331edfd739bd74a7f982746044d51c28aa3bbd0bf9be82a Agents are now available again across the platform. The issue has been resolved. https://status.langdock.com/incident/816724 Mon, 02 Feb 2026 07:31:00 -0000 https://status.langdock.com/incident/816724#de6484ca33409d271353890f478c0dd721cf3a8991f98687c0ce5dd2b9bf97f7 Agents are currently unavailable to browse or use across the platform. We have identified the root cause and are addressing it as soon as possible. https://status.langdock.com/ Sat, 31 Jan 2026 23:02:25 +0000 https://status.langdock.com/#8724250da6da3d920356643fbe9c153c62e95cc9b9ec87d430e90bc8db61bc1b Workflows Runtime recovered https://status.langdock.com/ Sat, 31 Jan 2026 22:50:32 +0000 https://status.langdock.com/#8724250da6da3d920356643fbe9c153c62e95cc9b9ec87d430e90bc8db61bc1b Workflows Runtime went down https://status.langdock.com/incident/813420 Wed, 28 Jan 2026 09:10:00 -0000 https://status.langdock.com/incident/813420#11f7f03b9b3e21d918790d4d3c25b3de6b63df727a375a94d36b3d45d508aa00 We're back! Thank you for your patience. https://status.langdock.com/ Wed, 28 Jan 2026 09:06:58 +0000 https://status.langdock.com/#a6a1b4660c046c7da7af2e5bd682dc888e7e5ecada4c15ff65743b9f6ae248a1 app.langdock.com recovered https://status.langdock.com/ Wed, 28 Jan 2026 09:06:21 +0000 https://status.langdock.com/#a6a1b4660c046c7da7af2e5bd682dc888e7e5ecada4c15ff65743b9f6ae248a1 app.langdock.com went down https://status.langdock.com/incident/813420 Wed, 28 Jan 2026 09:04:00 -0000 https://status.langdock.com/incident/813420#59f22e71010b6c4f1e81464ea3b4acee9cf90b505199d93abd522497769b2fe0 The platform is currently unavailable. We're investigating and will update you shortly. https://status.langdock.com/incident/812686 Tue, 27 Jan 2026 17:50:00 -0000 https://status.langdock.com/incident/812686#17a0a11a37525eb65e5c656058de7828b5cdfbd666f263ebc544663b9287eebc Azure resolved the issue, models are back to normal: https://azure.status.microsoft/en-us/status https://status.langdock.com/incident/812686 Tue, 27 Jan 2026 08:00:00 -0000 https://status.langdock.com/incident/812686#19971624656a172c6703233d28a99dad40ae1c3695eee3bfd34f87cd0f38784f Microsoft Azure is currently experiencing a downtime across its OpenAI Services in the Sweden Central region: https://azure.status.microsoft/en-us/status This is affecting users who configured their own OpenAI models hosted in the Sweden Central region. As a workaround, we recommend deploying the models in a different (EU) region. If you use the models provided by Langdock, this does not affect you. https://status.langdock.com/ Tue, 27 Jan 2026 02:26:41 +0000 https://status.langdock.com/#9fa3a20772803197eb31040b5582f3c9d6dedd5b7287bbd62ec420da7dca9237 Workflows Runtime recovered https://status.langdock.com/ Tue, 27 Jan 2026 02:12:06 +0000 https://status.langdock.com/#9fa3a20772803197eb31040b5582f3c9d6dedd5b7287bbd62ec420da7dca9237 Workflows Runtime went down https://status.langdock.com/incident/804580 Wed, 14 Jan 2026 21:14:00 -0000 https://status.langdock.com/incident/804580#5fa43eaf6c4f910fbe5fd017378133231dd1b76f5b9a4459234b90487ea0b92f Image generation is available again, thank you for your patience! https://status.langdock.com/incident/804580 Wed, 14 Jan 2026 19:20:00 -0000 https://status.langdock.com/incident/804580#1601d7a0816be6ead53e3d7a3536976251267b2477cb5dbee3b75e0272cf3568 Image generation is temporarily unavailable across the platform. We're aware of the issue and working on a fix. https://status.langdock.com/incident/799246 Tue, 06 Jan 2026 10:09:00 -0000 https://status.langdock.com/incident/799246#5f707808cf60a4972a985fa41f894f4b78224548795fbdef10afff54eb9051b8 The issue has been resolved. Thank you for your patience. https://status.langdock.com/incident/799246 Tue, 06 Jan 2026 09:34:00 -0000 https://status.langdock.com/incident/799246#262d8a6b83994613ad44d555ffe584c76c681ccb6230a6eb305019f607b9e55a We’ve identified the issue and confirmed that it only affects users with multiple workspaces. We’re working on a fix. https://status.langdock.com/incident/799246 Tue, 06 Jan 2026 09:00:00 -0000 https://status.langdock.com/incident/799246#d3941d22bff635da1b028957040581520cb9a0fc752138aca78695dea0ea7bcb Users who have multiple workspaces are currently unable to log in to the Langdock platform. We’re investigating the issue and will provide updates as they become available. https://status.langdock.com/incident/782865 Tue, 09 Dec 2025 09:45:00 -0000 https://status.langdock.com/incident/782865#0da7d79754a9fcca58ca1fef7d6f9fe20445dbd25dee6ee72d4f2e538ab9f418 We're back! Thank you for your patience. https://status.langdock.com/incident/782865 Tue, 09 Dec 2025 09:34:00 -0000 https://status.langdock.com/incident/782865#25a34c8a1d22670498b450286c6024c1d2b5b1af295c35929e92f968b859a778 The platform is currently unavailable. We're investigating and will update you shortly. https://status.langdock.com/incident/779560 Thu, 04 Dec 2025 10:59:00 -0000 https://status.langdock.com/incident/779560#4b031cbb42a5f9645a1c8d758c873e636f4128f0bfe59fdb6c766c83ab63c661 We're back! Thank you for for your patience. https://status.langdock.com/incident/779560 Thu, 04 Dec 2025 10:52:00 -0000 https://status.langdock.com/incident/779560#e022a912c63cc623c68013059f56a24377a3ef4bba6f6946d3acc4fc645f5fcf The platform is currently unavailable and users are being logged out. https://status.langdock.com/incident/770904 Thu, 20 Nov 2025 11:13:00 -0000 https://status.langdock.com/incident/770904#45c899e9f2cfcd1e352d7f3a398c818b3b1379d3d39d5559fc184b79f5b6906d We're back! Thank you for your patience. https://status.langdock.com/incident/770904 Thu, 20 Nov 2025 11:07:00 -0000 https://status.langdock.com/incident/770904#eaee7c5ea143164fe9ef0742ffa3f6f2f9d05a8f2ee30943b21dd9a084505cf4 Langdock is currently unavailable due to an error in our update process. We're gonna be live again in 5 minutes. https://status.langdock.com/incident/768479 Tue, 18 Nov 2025 14:34:00 -0000 https://status.langdock.com/incident/768479#f944499badbd841f0a7b6b4fe65e3f87afa19e9fd3ffddc8e1cf533e0aec8d5c Cloudflare has resolved the issues affecting their edge network, and the Langdock application is now operating normally again. All services are fully restored, and users should no longer experience any disruptions or performance degradation. We will continue to monitor the situation closely to ensure everything remains stable and responsive. https://status.langdock.com/incident/768479 Tue, 18 Nov 2025 12:19:00 -0000 https://status.langdock.com/incident/768479#f0263b642aa19146fc1d974101fdddb0d8a5ac0a4d1db299932f40e2e60f54b6 Similar to many internet platforms, we use Cloudflare to protect our services, which is currently experiencing downtime. You can read more about the underlying incident on Cloudflare's status page: https://www.cloudflarestatus.com/ According to their estimates, it will be resolved soon. We're going to update you as soon as we know more. https://status.langdock.com/incident/768479 Tue, 18 Nov 2025 11:38:00 -0000 https://status.langdock.com/incident/768479#b7779bbae2764f5ed09822a722e19255da2d1614a3e706b9b352dabddcccb96d Currently our platform is not available, possibly due to Cloudflare issues in multiple regions. We're investigating. https://status.langdock.com/incident/767505 Mon, 17 Nov 2025 15:39:00 -0000 https://status.langdock.com/incident/767505#e156fe749badc43e60eff88ce8248fd914fcfded4982f2763c37d382fddf68e9 We're back! Thanks for your patience https://status.langdock.com/incident/767505 Mon, 17 Nov 2025 15:34:00 -0000 https://status.langdock.com/incident/767505#438f52411024bb4c3bc8e088563b4d49e8a09742013f5a50dff24ff616c82abd Langdock is currently not available. We're working on a fix and should be live within the next minutes. https://status.langdock.com/incident/763019 Wed, 12 Nov 2025 15:57:00 -0000 https://status.langdock.com/incident/763019#6d27cd750f54f83fb241fac4a7055326328a43f20b163699a883d92f5a3363df We're back! The root cause was a database maintenance job that took longer than anticipated. https://status.langdock.com/incident/763019 Wed, 12 Nov 2025 15:45:00 -0000 https://status.langdock.com/incident/763019#82567a67ff151e3fbc8a24ef70d2b73bd6eb4914a20a9aaf2b74ecccb751c695 The Langdock platform is currently unavailable. We're aware of the issue and are working on a fix. https://status.langdock.com/incident/759023 Thu, 06 Nov 2025 06:40:00 -0000 https://status.langdock.com/incident/759023#9216eba08c0f489c940cf80fbdb4afe2bc945b6557b710934c7d875e598e66c7 We have identified the root cause and fixed the issue by upgrading our system that handles background jobs. https://status.langdock.com/incident/759023 Thu, 06 Nov 2025 05:40:00 -0000 https://status.langdock.com/incident/759023#bd5e88c2bd68bd2e4a323b2ea7513a62e89560100d44059b3babab972bc5baf5 Documents can't be uploaded of imported into the Langdock platform, we're aware of the issue and actively working on resolving it. https://status.langdock.com/incident/754419 Thu, 30 Oct 2025 10:49:00 -0000 https://status.langdock.com/incident/754419#2d5d7ee1adfa6f1fc94c086a9519faef13192e81d4501b86e803f11773706c57 The issue is now resolved. If document upload is not working for you, please try refreshing your browser window or clear your browser cache. https://status.langdock.com/incident/754419 Thu, 30 Oct 2025 10:08:00 -0000 https://status.langdock.com/incident/754419#037799473239b6ffc6345f68a4be6dee5e00d02e3b368112c5a2fc89bb337162 Documents currently can't be uploaded on the platform. We identified the root cause and are working on a fix already. https://status.langdock.com/incident/752960 Tue, 28 Oct 2025 13:49:00 -0000 https://status.langdock.com/incident/752960#cec6ea07cfc79656880bc631e744619df6a640bcc2349447613031c5786ee965 We have identified the root cause of the issue and resolved it. The platform is now available again. https://status.langdock.com/incident/752960 Tue, 28 Oct 2025 13:35:00 -0000 https://status.langdock.com/incident/752960#13f79661c72151ee940dfedaf21d374eb0d289e93684637b917c6c2ff873665c The team has noticed increased error rates across the Langdock platform. We are investigating the issue actively and will update you shortly. https://status.langdock.com/incident/749109 Wed, 22 Oct 2025 09:58:00 -0000 https://status.langdock.com/incident/749109#c6201a34735505013a251d0805b0cf36e4bc7912f851d6a46f9a025f84fdd798 Integrations are enabled again. This incident is resolved. https://status.langdock.com/incident/749109 Wed, 22 Oct 2025 08:38:00 -0000 https://status.langdock.com/incident/749109#1651bc06e8b6e0b9bd09d1842b41abc0a5baedf2a7e5eb73d5b237eb5cf5d1e1 We have temporarily disabled integration actions in chat and the integrations page for performance reasons. We are actively working on re-enabling it and will provide an update on that soon. https://status.langdock.com/incident/743949 Wed, 15 Oct 2025 09:31:00 -0000 https://status.langdock.com/incident/743949#f7d2b64aad2700cb541957d907522e412c741f27c0519e6d845aa682d03cb28b We're back! We identified the root cause and deployed a quick fix. Currently, knowledge folders can't be tagged in the chat. We will release a long-term fix for this soon. https://status.langdock.com/incident/743949 Wed, 15 Oct 2025 09:22:00 -0000 https://status.langdock.com/incident/743949#fb1bf1a5930755eb2bdf7c0f7cb4e0fdd431eebd33d39f89164e3ec79fa16af5 The platform performance is impacted. We are investigating and will provide an update shortly. https://status.langdock.com/incident/743915 Wed, 15 Oct 2025 08:47:00 -0000 https://status.langdock.com/incident/743915#75474313d91bbf8ff872d99d5ff76d0b9ac5949c8c5ef619ceea77752f495b37 The incident is resolved. Performance is back to normal levels. https://status.langdock.com/incident/743915 Wed, 15 Oct 2025 08:41:00 -0000 https://status.langdock.com/incident/743915#b918986e5e5c89d0f74cb5d9dbabad9d12e68398585b0c6bb81c98ea9367d280 The platform performance is currently degraded with the page taking a longer time to load and prompts taking longer to get an answer. We are investigating and will provide an update shortly. https://status.langdock.com/incident/743459 Tue, 14 Oct 2025 14:32:00 -0000 https://status.langdock.com/incident/743459#1e7ac40a69a64dfbcc0e6388eae37f9a5b80a822833c046aa603aeb4826691cd We're back! Thanks for your patience https://status.langdock.com/incident/743459 Tue, 14 Oct 2025 14:28:00 -0000 https://status.langdock.com/incident/743459#6e9f2ed9ea0344f6ea985bdfc09a5905ebb53ef1458b8ca8b84f69a981786642 We're performing a short unplanned update on our systems, which results in a 5 minute downtime https://status.langdock.com/incident/743437 Tue, 14 Oct 2025 14:13:00 -0000 https://status.langdock.com/incident/743437#f524d325e5e32a990a4f66a96672bae0043bb3106e53672030794b60f4487c1d We're back, the platform is operating as usual. https://status.langdock.com/incident/743437 Tue, 14 Oct 2025 13:48:00 -0000 https://status.langdock.com/incident/743437#442ea66af4f96257193a80f478b3526cdd7eadddc40ef45164006e22f1d8f90a The Langdock platform is currently slow for all users. We're investigating and will publish an update soon. Thanks for your patience! https://status.langdock.com/incident/741115 Fri, 10 Oct 2025 10:31:00 -0000 https://status.langdock.com/incident/741115#6805f66c5db2ffdf4640d2fc1bc126f21825a30ee2a0100bef8eb1b4e3bca728 We're back! All models are stable again. https://status.langdock.com/incident/741115 Fri, 10 Oct 2025 10:10:00 -0000 https://status.langdock.com/incident/741115#d062b736848089f0ae350b24e7b57e3b975a18af83edf82a7914aae3c2c5fad0 We're currently experiencing issues on our platform where is some cases, models don't respond to user prompts. We’re working to fix the problem as quickly as we can. As a workaround, we recommend retrying a prompt with the same model in the same conversation. https://status.langdock.com/incident/739282 Tue, 07 Oct 2025 13:44:00 -0000 https://status.langdock.com/incident/739282#1e1e95561d45f89165206c8d5e04cb031b5f443efebf1e7b27515cd9f3683334 The issues are resolved. https://status.langdock.com/incident/739282 Tue, 07 Oct 2025 13:37:00 -0000 https://status.langdock.com/incident/739282#8544018dd022efef5736cf5196718c1322bedd11b42492611523365aeb619043 The platform is currently experiencing increased latency and failed requests. We are investigating and will provide an update shortly. https://status.langdock.com/incident/739177 Tue, 07 Oct 2025 10:09:00 -0000 https://status.langdock.com/incident/739177#07a9fa039c78cd3cc8eeca4533b7a911f42f1a1b6c3f5c0fc1132bb87cfdbe62 We’re back! We’ve upgraded our system, and everything should be running as usual. Thanks for your patience! https://status.langdock.com/incident/739177 Tue, 07 Oct 2025 09:55:00 -0000 https://status.langdock.com/incident/739177#c6383d5c5814a4fb66c9f8f4c4b15e52826b6cc57f37304ade9b321a73d9c704 We're experiencing some degraded performance and taking preventive measures by upgrading our system. This will result in a 15 minute downtime. https://status.langdock.com/incident/735035 Tue, 30 Sep 2025 14:49:00 -0000 https://status.langdock.com/incident/735035#50ec7533d3b77a97c060d11a0143c48815e2ce547888d09e29295570d856be6d We're back! All models stable. We're actively working on preventive measures to ensure this doesn't happen again. https://status.langdock.com/incident/735035 Tue, 30 Sep 2025 14:04:00 -0000 https://status.langdock.com/incident/735035#c32bec77f7f13a566717fbb1da819be67af712bf4068eb2f10d0fc46547012d6 We're currently experiencing issues on our platform where is some cases, models don't respond to user prompts. We’re working to fix the problem as quickly as we can. As a workaround, we recommend retrying a prompt with the same model in the same conversation. https://status.langdock.com/incident/730977 Tue, 23 Sep 2025 21:17:00 -0000 https://status.langdock.com/incident/730977#110454e31ace23d657e92971cefe9778f8020f565fbea898ba198bb38c24c37d We have identified and fixed the root cause of the issue. AI models are available again across the product. Thank you for your patience! https://status.langdock.com/incident/730977 Tue, 23 Sep 2025 20:33:00 -0000 https://status.langdock.com/incident/730977#08a8f6d185d21b472f60a2623227f53aad7f27f6d951739a4019d951c3333073 We’re investigating an issue with AI models that is impacting all users. We’re working to fix the problem as quickly as we can. We’ll share another update shortly. https://status.langdock.com/incident/299614 Wed, 13 Dec 2023 09:00:00 -0000 https://status.langdock.com/incident/299614#6b35cf7e185c4f1d9764b462d5cffb1fc7ed3af1446cc50f21301424442105c2 Maintenance completed https://status.langdock.com/incident/299614 Wed, 13 Dec 2023 07:00:00 -0000 https://status.langdock.com/incident/299614#7eb96daab02a4cb310b63af33d6456c2d32f552768a9488aa5845d01edab1251 We are updating the queueing mechanism of the Langdock platform. While this should not have an impact on the availability of the platform, there could occur some minor interruptions when uploading or importing documents.