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 Jul 2026 20:02:02 +0000 https://status.langdock.com/#a5b02e8668cf96cddb28ad7bd4c9392a787c809b7311e04a03e42e9809d7c44e Workflows Runtime recovered https://status.langdock.com/ Wed, 15 Jul 2026 19:42:42 +0000 https://status.langdock.com/#a5b02e8668cf96cddb28ad7bd4c9392a787c809b7311e04a03e42e9809d7c44e Workflows Runtime went down https://status.langdock.com/ Wed, 15 Jul 2026 12:27:16 +0000 https://status.langdock.com/#c9af21fb7661cd2f8472ec5e7f4ca8b162e792113526cefa51bc1b117f3b1e6a Workflows Runtime recovered https://status.langdock.com/ Wed, 15 Jul 2026 12:00:58 +0000 https://status.langdock.com/#c9af21fb7661cd2f8472ec5e7f4ca8b162e792113526cefa51bc1b117f3b1e6a Workflows Runtime went down https://status.langdock.com/ Tue, 14 Jul 2026 13:23:12 +0000 https://status.langdock.com/#63c0b1a0a5901773c59697f21580d0680789acef275651f7314fbd70eae5011d Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Jul 2026 13:17:29 +0000 https://status.langdock.com/#63c0b1a0a5901773c59697f21580d0680789acef275651f7314fbd70eae5011d Workflows Runtime went down https://status.langdock.com/ Tue, 14 Jul 2026 13:06:04 +0000 https://status.langdock.com/#7be67c3b2c834d1b1ade4b877bdeb48d8d6420817a9909f87681e69bba0d7ecb Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Jul 2026 12:02:04 +0000 https://status.langdock.com/#7be67c3b2c834d1b1ade4b877bdeb48d8d6420817a9909f87681e69bba0d7ecb Workflows Runtime went down https://status.langdock.com/ Tue, 14 Jul 2026 11:46:40 +0000 https://status.langdock.com/#29029e31c9c93d55facc9bcc70b23a3fffb783b374516fac85e285945e936bfd Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Jul 2026 11:45:19 +0000 https://status.langdock.com/#29029e31c9c93d55facc9bcc70b23a3fffb783b374516fac85e285945e936bfd Workflows Runtime went down https://status.langdock.com/ Tue, 14 Jul 2026 09:32:30 +0000 https://status.langdock.com/#99acbabf629b86bf1a28c9a354d6b6a09f9de5ed590111283139d0a5eab7e532 Workflows Runtime recovered https://status.langdock.com/ Tue, 14 Jul 2026 09:30:55 +0000 https://status.langdock.com/#99acbabf629b86bf1a28c9a354d6b6a09f9de5ed590111283139d0a5eab7e532 Workflows Runtime went down https://status.langdock.com/ Mon, 13 Jul 2026 08:18:12 +0000 https://status.langdock.com/#4f40cb9f5bb24b861d8ed08b6956cb1698622e0b32c4ef8c1f3334dc68e975c8 Workflows Runtime recovered https://status.langdock.com/ Mon, 13 Jul 2026 08:15:00 +0000 https://status.langdock.com/#4f40cb9f5bb24b861d8ed08b6956cb1698622e0b32c4ef8c1f3334dc68e975c8 Workflows Runtime went down https://status.langdock.com/ Mon, 13 Jul 2026 08:02:33 +0000 https://status.langdock.com/#1828c3f07cb5976808d6c73248fd5b6a927fe439c5a310ed54ca6b6e14450b75 Workflows Runtime recovered https://status.langdock.com/ Mon, 13 Jul 2026 08:00:49 +0000 https://status.langdock.com/#1828c3f07cb5976808d6c73248fd5b6a927fe439c5a310ed54ca6b6e14450b75 Workflows Runtime went down https://status.langdock.com/ Mon, 13 Jul 2026 07:14:03 +0000 https://status.langdock.com/#9c237b315a35962361a2e3091cf2c79274d6805346c9014834c1c871dd549646 Workflows Runtime recovered https://status.langdock.com/ Mon, 13 Jul 2026 07:10:56 +0000 https://status.langdock.com/#9c237b315a35962361a2e3091cf2c79274d6805346c9014834c1c871dd549646 Workflows Runtime went down https://status.langdock.com/ Sun, 12 Jul 2026 11:42:06 +0000 https://status.langdock.com/#c5a9c2bed1206ea21de86e4f7fc5411182561407a7f2995174772304c9ec991d app.langdock.com recovered https://status.langdock.com/ Sun, 12 Jul 2026 11:41:28 +0000 https://status.langdock.com/#c5a9c2bed1206ea21de86e4f7fc5411182561407a7f2995174772304c9ec991d app.langdock.com went down https://status.langdock.com/incident/948179 Fri, 10 Jul 2026 21:00:51 -0000 https://status.langdock.com/incident/948179#c8461c936669ed24ec5efde5d5f0d8ee65785759f26d02c5292d0ae50d9a1304 We're performing planned database maintenance to change our replication mode, enabling read replicas and Change Data Capture (CDC) for improved scalability and reliability. While we've reserved a short maintenance window, we expect any disruption to last only a few seconds to minutes, during which Langdock may be briefly unavailable or slower than usual. No data will be affected. We've scheduled this during off-peak hours to minimize disruption. Thank you for your patience! The Langdock Team https://status.langdock.com/ Fri, 10 Jul 2026 09:53:19 +0000 https://status.langdock.com/#1e6fe80afc929375db013235a159f836cdd8fef1a468ecdf173981f4bcfe0a2c Workflows Runtime recovered https://status.langdock.com/ Fri, 10 Jul 2026 09:51:38 +0000 https://status.langdock.com/#1e6fe80afc929375db013235a159f836cdd8fef1a468ecdf173981f4bcfe0a2c Workflows Runtime went down https://status.langdock.com/ Fri, 10 Jul 2026 09:45:05 +0000 https://status.langdock.com/#5d502a25c40ebc10382779bc696ac93e7eb9ff6aaac1f48eb45413b445a7902a Workflows Runtime recovered https://status.langdock.com/ Fri, 10 Jul 2026 09:36:11 +0000 https://status.langdock.com/#5d502a25c40ebc10382779bc696ac93e7eb9ff6aaac1f48eb45413b445a7902a Workflows Runtime went down https://status.langdock.com/ Fri, 10 Jul 2026 09:28:31 +0000 https://status.langdock.com/#1011c8f759e5c17d3a21958411389ac5041dc22b77770af0a455999f48db3d79 Workflows Runtime recovered https://status.langdock.com/ Fri, 10 Jul 2026 09:24:13 +0000 https://status.langdock.com/#1011c8f759e5c17d3a21958411389ac5041dc22b77770af0a455999f48db3d79 Workflows Runtime went down https://status.langdock.com/ Tue, 07 Jul 2026 12:32:20 +0000 https://status.langdock.com/#3a730042b12c3c8f1bef87672bb54cb4f502c3c7dcc6743e1dc0e81f5e2916e4 Workflows Runtime recovered https://status.langdock.com/ Tue, 07 Jul 2026 11:53:23 +0000 https://status.langdock.com/#3a730042b12c3c8f1bef87672bb54cb4f502c3c7dcc6743e1dc0e81f5e2916e4 Workflows Runtime went down https://status.langdock.com/ Tue, 07 Jul 2026 11:53:12 +0000 https://status.langdock.com/#0d86f59c2ba57ce62d53a9973a7afb850571a4fb4bc5ca0ad86520f210e314a4 Workflows Runtime recovered https://status.langdock.com/ Tue, 07 Jul 2026 11:47:33 +0000 https://status.langdock.com/#0d86f59c2ba57ce62d53a9973a7afb850571a4fb4bc5ca0ad86520f210e314a4 Workflows Runtime went down https://status.langdock.com/ Tue, 07 Jul 2026 11:46:46 +0000 https://status.langdock.com/#1316facdb1eb0ab55f70c69e3494552a38c73cd7f4de059dce4bf4efc06fa9ff Workflows Runtime recovered https://status.langdock.com/ Tue, 07 Jul 2026 11:09:38 +0000 https://status.langdock.com/#1316facdb1eb0ab55f70c69e3494552a38c73cd7f4de059dce4bf4efc06fa9ff Workflows Runtime went down https://status.langdock.com/ Tue, 07 Jul 2026 11:09:15 +0000 https://status.langdock.com/#17be5b350a20d4e5a192d151e4b0eb7647a58a203d7776ba3ab51d0d737223bc Workflows Runtime recovered https://status.langdock.com/ Tue, 07 Jul 2026 11:06:43 +0000 https://status.langdock.com/#17be5b350a20d4e5a192d151e4b0eb7647a58a203d7776ba3ab51d0d737223bc Workflows Runtime went down https://status.langdock.com/incident/940800 Wed, 01 Jul 2026 18:53:00 -0000 https://status.langdock.com/incident/940800#659530b4c923122c547e56eaf8cf981771c0fcb1f11c6ed941932824dc0289d3 We have identified the root cause and fixed the issue. Claude models should be working as expected. https://status.langdock.com/incident/940800 Wed, 01 Jul 2026 18:19:00 -0000 https://status.langdock.com/incident/940800#968844738a226548a930206214e4c4b377da95b8b068736b653ad4a15a55928d Claude models provided by Langdock are currently unavailable. Chat requests will fall back to another model. We're investigating. https://status.langdock.com/ Mon, 22 Jun 2026 17:29:06 +0000 https://status.langdock.com/#6b3a70ecdbabe6f5e2a80ed24f76b3ab1a36d5beccabb30da8a9200d9f473ff5 api.langdock.com recovered https://status.langdock.com/ Mon, 22 Jun 2026 17:21:07 +0000 https://status.langdock.com/#6b3a70ecdbabe6f5e2a80ed24f76b3ab1a36d5beccabb30da8a9200d9f473ff5 api.langdock.com went down https://status.langdock.com/ Sun, 21 Jun 2026 02:56:38 +0000 https://status.langdock.com/#cc1a4579bff6dac6ffe0415e6268ea7093b4a255aadb8196f8ec9a98e187ef67 Workflows Runtime recovered https://status.langdock.com/ Sun, 21 Jun 2026 02:54:58 +0000 https://status.langdock.com/#cc1a4579bff6dac6ffe0415e6268ea7093b4a255aadb8196f8ec9a98e187ef67 Workflows Runtime went down https://status.langdock.com/ Sun, 21 Jun 2026 02:42:27 +0000 https://status.langdock.com/#d6a1f9fc8a547804a54704f77f169785d815cc838be736e21001e9ff47ed4d9f Workflows Runtime recovered https://status.langdock.com/ Sun, 21 Jun 2026 02:39:24 +0000 https://status.langdock.com/#d6a1f9fc8a547804a54704f77f169785d815cc838be736e21001e9ff47ed4d9f Workflows Runtime went down https://status.langdock.com/ Sun, 21 Jun 2026 02:20:31 +0000 https://status.langdock.com/#72cb853ba28791a53025d10ef2927a4cd027cd6048c56a6bbb021f633bb82ce6 Workflows Runtime recovered https://status.langdock.com/ Sun, 21 Jun 2026 02:19:21 +0000 https://status.langdock.com/#72cb853ba28791a53025d10ef2927a4cd027cd6048c56a6bbb021f633bb82ce6 Workflows Runtime went down https://status.langdock.com/ Sat, 20 Jun 2026 03:22:28 +0000 https://status.langdock.com/#6428fd3c8677c35db37e2780808352204e8ecc393dd6a86fa875f4d2f0dfb4a3 Workflows Runtime recovered https://status.langdock.com/ Sat, 20 Jun 2026 03:20:33 +0000 https://status.langdock.com/#6428fd3c8677c35db37e2780808352204e8ecc393dd6a86fa875f4d2f0dfb4a3 Workflows Runtime went down https://status.langdock.com/ Sat, 20 Jun 2026 03:08:19 +0000 https://status.langdock.com/#b626adb6f728a40762f6c1ffbc53ee6707877c7f2f7777857006c2118eb3a348 Workflows Runtime recovered https://status.langdock.com/ Sat, 20 Jun 2026 03:06:41 +0000 https://status.langdock.com/#b626adb6f728a40762f6c1ffbc53ee6707877c7f2f7777857006c2118eb3a348 Workflows Runtime went down https://status.langdock.com/ Sat, 20 Jun 2026 01:30:26 +0000 https://status.langdock.com/#1db147044c8dcbe3ade374b59251025fea945d150f26c7b6fb9c9f3999a849b5 Workflows Runtime recovered https://status.langdock.com/ Sat, 20 Jun 2026 01:28:55 +0000 https://status.langdock.com/#1db147044c8dcbe3ade374b59251025fea945d150f26c7b6fb9c9f3999a849b5 Workflows Runtime went down https://status.langdock.com/incident/928747 Fri, 19 Jun 2026 12:27:00 -0000 https://status.langdock.com/incident/928747#58af15fe48ac91e006d0dc89b52adffe87827634714f96b1af7f09c206cf4e67 The issue is now resolved. Langdock is back to normal. https://status.langdock.com/incident/928747 Fri, 19 Jun 2026 12:18:00 -0000 https://status.langdock.com/incident/928747#9c0f825c172301f89fb8e7a353ae27fe130ed3ec893b0ff52584a77918df8313 Langdock is currently slow for most users. We have identified the underlying issue and expect to resolve within the next 10 minutes. https://status.langdock.com/ Fri, 19 Jun 2026 10:44:59 +0000 https://status.langdock.com/#e6fe451ae1baf3218d53717047c688da3d033f000aa287a03dc29ee2747e25d3 app.langdock.com recovered https://status.langdock.com/ Fri, 19 Jun 2026 10:42:40 +0000 https://status.langdock.com/#e6fe451ae1baf3218d53717047c688da3d033f000aa287a03dc29ee2747e25d3 app.langdock.com went down https://status.langdock.com/ Thu, 18 Jun 2026 04:23:04 +0000 https://status.langdock.com/#3c78d081565add3fb902d3cee3299ebda1502035a686fcfa43486821e23b6993 Workflows Runtime recovered https://status.langdock.com/ Thu, 18 Jun 2026 03:55:22 +0000 https://status.langdock.com/#3c78d081565add3fb902d3cee3299ebda1502035a686fcfa43486821e23b6993 Workflows Runtime went down https://status.langdock.com/ Wed, 17 Jun 2026 20:05:25 +0000 https://status.langdock.com/#0f3b11bb7a71efef777db486dcb9706057c6062407681ca90620a320ee616f46 Workflows Runtime recovered https://status.langdock.com/ Wed, 17 Jun 2026 20:04:47 +0000 https://status.langdock.com/#0f3b11bb7a71efef777db486dcb9706057c6062407681ca90620a320ee616f46 Workflows Runtime went down https://status.langdock.com/ Wed, 17 Jun 2026 08:21:49 +0000 https://status.langdock.com/#1a02bd19d04e442fe487981e8d0f295f87fd4b77e1c275b6173ce6424dc0f779 Workflows Runtime recovered https://status.langdock.com/ Wed, 17 Jun 2026 08:20:46 +0000 https://status.langdock.com/#1a02bd19d04e442fe487981e8d0f295f87fd4b77e1c275b6173ce6424dc0f779 Workflows Runtime went down https://status.langdock.com/ Wed, 17 Jun 2026 07:37:41 +0000 https://status.langdock.com/#344094d9cb1268b7857b91db3d583c9d3b87c892a8ff158cec6478ce3a8f9e33 Workflows Runtime recovered https://status.langdock.com/ Wed, 17 Jun 2026 07:35:35 +0000 https://status.langdock.com/#344094d9cb1268b7857b91db3d583c9d3b87c892a8ff158cec6478ce3a8f9e33 Workflows Runtime went down https://status.langdock.com/ Wed, 17 Jun 2026 07:29:13 +0000 https://status.langdock.com/#3dd90aea3abb5c177044ca42b49f3af287679fe8b30d5196077c437e7d3d1023 Workflows Runtime recovered https://status.langdock.com/ Wed, 17 Jun 2026 07:23:27 +0000 https://status.langdock.com/#7f100f90b58d9504d9be5c670e7f792dec071f406dc5b7a70554b3737d513544 app.langdock.com recovered https://status.langdock.com/ Wed, 17 Jun 2026 06:58:01 +0000 https://status.langdock.com/#3dd90aea3abb5c177044ca42b49f3af287679fe8b30d5196077c437e7d3d1023 Workflows Runtime went down https://status.langdock.com/ Wed, 17 Jun 2026 06:54:45 +0000 https://status.langdock.com/#7f100f90b58d9504d9be5c670e7f792dec071f406dc5b7a70554b3737d513544 app.langdock.com went down https://status.langdock.com/ Tue, 16 Jun 2026 15:16:45 +0000 https://status.langdock.com/#67d935490093cb8be81f4f1dd82b53d6feab8044a49d6b3278d5ae0c46dc7a1d Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 15:14:46 +0000 https://status.langdock.com/#67d935490093cb8be81f4f1dd82b53d6feab8044a49d6b3278d5ae0c46dc7a1d Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 14:45:42 +0000 https://status.langdock.com/#344fefda457140db5220a65604a47a1f1db0cda9fe4f8d48a62d11ccc960fd81 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 14:41:57 +0000 https://status.langdock.com/#344fefda457140db5220a65604a47a1f1db0cda9fe4f8d48a62d11ccc960fd81 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 14:16:26 +0000 https://status.langdock.com/#8e6260a3e3a7cc04066663d1bb9cda3d4f84920eb1bf88b14170415574b795ee Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 14:14:54 +0000 https://status.langdock.com/#8e6260a3e3a7cc04066663d1bb9cda3d4f84920eb1bf88b14170415574b795ee Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 13:53:12 +0000 https://status.langdock.com/#a5b4404ff80246e61fcecc02420d442a845fb6191a782d22793ab612371fef6e Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 13:46:10 +0000 https://status.langdock.com/#a5b4404ff80246e61fcecc02420d442a845fb6191a782d22793ab612371fef6e Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 13:40:34 +0000 https://status.langdock.com/#22c65c06cc93939ce638ee5bcfc3519a912e92bfbb12203846157815bedba049 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 13:38:53 +0000 https://status.langdock.com/#22c65c06cc93939ce638ee5bcfc3519a912e92bfbb12203846157815bedba049 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 13:05:08 +0000 https://status.langdock.com/#7354ecaec894950973929e1ed83790bb478f955aa9840744de7b20289e7fd506 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 12:59:03 +0000 https://status.langdock.com/#7354ecaec894950973929e1ed83790bb478f955aa9840744de7b20289e7fd506 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 12:47:51 +0000 https://status.langdock.com/#95fa9862246d8a94ab3e33656c9c5d34d1c542e73e1d312b8f75c5716b39dc9e Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 12:43:03 +0000 https://status.langdock.com/#95fa9862246d8a94ab3e33656c9c5d34d1c542e73e1d312b8f75c5716b39dc9e Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 12:42:59 +0000 https://status.langdock.com/#0c41c63eb68f85cc7df98d6dfd5533e2b477654bbe07bd40231dddac2f1f9d64 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 12:42:10 +0000 https://status.langdock.com/#0c41c63eb68f85cc7df98d6dfd5533e2b477654bbe07bd40231dddac2f1f9d64 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 12:36:34 +0000 https://status.langdock.com/#4e7d6dc9f0084b7ad9f6aa589932f91c6d1890817c6053239a4e9956773900fb Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 12:34:56 +0000 https://status.langdock.com/#4e7d6dc9f0084b7ad9f6aa589932f91c6d1890817c6053239a4e9956773900fb Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 12:25:03 +0000 https://status.langdock.com/#2e11287d29d894712dcf8bfb006e7e8afe6726a2a89c1ef030e9041e73bface2 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 12:22:11 +0000 https://status.langdock.com/#2e11287d29d894712dcf8bfb006e7e8afe6726a2a89c1ef030e9041e73bface2 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 11:54:48 +0000 https://status.langdock.com/#7e34f3bcb8af3e702712eb9426c965fcb4abe0618a022aafb7c3b3d76b73a63b Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 11:52:03 +0000 https://status.langdock.com/#7e34f3bcb8af3e702712eb9426c965fcb4abe0618a022aafb7c3b3d76b73a63b Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 11:42:36 +0000 https://status.langdock.com/#c3012c30cd52c7b6f9376807c202f083c8246eb2218c17ce5893abb2a2fbd6b5 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 11:40:39 +0000 https://status.langdock.com/#c3012c30cd52c7b6f9376807c202f083c8246eb2218c17ce5893abb2a2fbd6b5 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 11:17:19 +0000 https://status.langdock.com/#7f7d92820458b7cf4f3d458927c0cfd38039bb09cc52508fd0f0bf2a9d963a48 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 11:16:39 +0000 https://status.langdock.com/#7f7d92820458b7cf4f3d458927c0cfd38039bb09cc52508fd0f0bf2a9d963a48 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 10:15:30 +0000 https://status.langdock.com/#550e7ab6dd707cd0151d9ce7bd578f7465ecce978f103d9f798eefe5030d5fe2 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 10:13:56 +0000 https://status.langdock.com/#550e7ab6dd707cd0151d9ce7bd578f7465ecce978f103d9f798eefe5030d5fe2 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 09:55:11 +0000 https://status.langdock.com/#7e31fb6adb7be3cde5ec3b68fb2958380fb4ccabc0358ba5c0c5987f46a847f2 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 09:53:56 +0000 https://status.langdock.com/#7e31fb6adb7be3cde5ec3b68fb2958380fb4ccabc0358ba5c0c5987f46a847f2 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 09:46:07 +0000 https://status.langdock.com/#3f6d30b41e7d0fa62186547a332ee80f60547228fdeae3ce11e052b0860d592c Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 09:45:33 +0000 https://status.langdock.com/#3f6d30b41e7d0fa62186547a332ee80f60547228fdeae3ce11e052b0860d592c Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 09:31:09 +0000 https://status.langdock.com/#da61fbfd37b72e2b0b7b7e560ea4bb695018d951192985991965346a8c6a604d Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 09:29:55 +0000 https://status.langdock.com/#da61fbfd37b72e2b0b7b7e560ea4bb695018d951192985991965346a8c6a604d Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 09:08:40 +0000 https://status.langdock.com/#4ed0d224a1450eff261b754a09d2eb39973cf872e21d4191e59af33e0e1f230b Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 09:05:34 +0000 https://status.langdock.com/#4ed0d224a1450eff261b754a09d2eb39973cf872e21d4191e59af33e0e1f230b Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 09:04:01 +0000 https://status.langdock.com/#14db97f61b684d43e7e4598058a9e4ae5fbed1d22b59f689ca1147fd982d6491 app.langdock.com recovered https://status.langdock.com/ Tue, 16 Jun 2026 09:00:52 +0000 https://status.langdock.com/#14db97f61b684d43e7e4598058a9e4ae5fbed1d22b59f689ca1147fd982d6491 app.langdock.com went down https://status.langdock.com/ Tue, 16 Jun 2026 08:59:51 +0000 https://status.langdock.com/#aafa45ea5e0b8292b38b090a89266bd4990c7fde045e76cc49a7d915b4006971 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 08:58:06 +0000 https://status.langdock.com/#aafa45ea5e0b8292b38b090a89266bd4990c7fde045e76cc49a7d915b4006971 Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 08:55:09 +0000 https://status.langdock.com/#97a7f3b44bbaa3c2e692c43dfbce1cc17f53c17ee19d5fff6f82d05883ada550 app.langdock.com recovered https://status.langdock.com/ Tue, 16 Jun 2026 08:54:19 +0000 https://status.langdock.com/#97a7f3b44bbaa3c2e692c43dfbce1cc17f53c17ee19d5fff6f82d05883ada550 app.langdock.com went down https://status.langdock.com/ Tue, 16 Jun 2026 08:44:19 +0000 https://status.langdock.com/#d3568a63d7a76ae3fcbf3a570e765dc673f9d6123bcea4d8fcdf1728e076783b Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 08:41:34 +0000 https://status.langdock.com/#d3568a63d7a76ae3fcbf3a570e765dc673f9d6123bcea4d8fcdf1728e076783b Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 08:35:50 +0000 https://status.langdock.com/#ae84ac1ca0be74a725c20a04969be30f2d8e998d5a576621e39725ed7ef8a79d Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 08:34:02 +0000 https://status.langdock.com/#ae84ac1ca0be74a725c20a04969be30f2d8e998d5a576621e39725ed7ef8a79d Workflows Runtime went down https://status.langdock.com/ Tue, 16 Jun 2026 08:15:10 +0000 https://status.langdock.com/#e7bed5c66663e19026f131e6cf71f496e527ef9e546f0af3fc16c625155e7750 Workflows Runtime recovered https://status.langdock.com/ Tue, 16 Jun 2026 08:14:38 +0000 https://status.langdock.com/#e7bed5c66663e19026f131e6cf71f496e527ef9e546f0af3fc16c625155e7750 Workflows Runtime went down https://status.langdock.com/ Mon, 15 Jun 2026 06:05:41 +0000 https://status.langdock.com/#d7adfa2cb29fa86a4c6edb9df804631f94a274a28577035535f04e136c459209 Workflows Runtime recovered https://status.langdock.com/ Mon, 15 Jun 2026 06:05:10 +0000 https://status.langdock.com/#d7adfa2cb29fa86a4c6edb9df804631f94a274a28577035535f04e136c459209 Workflows Runtime went down https://status.langdock.com/ Fri, 12 Jun 2026 03:04:26 +0000 https://status.langdock.com/#e4663e672d64060297add66678b79820e0c2633aec79d7ef1c960c65eca1defb Workflows Runtime recovered https://status.langdock.com/ Fri, 12 Jun 2026 03:00:40 +0000 https://status.langdock.com/#e4663e672d64060297add66678b79820e0c2633aec79d7ef1c960c65eca1defb Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 09:44:10 +0000 https://status.langdock.com/#7a3f514d3c3312466190bd90b0ad21b051ffe40c39a4a249c3f84dc32ce1256e Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 09:42:09 +0000 https://status.langdock.com/#7a3f514d3c3312466190bd90b0ad21b051ffe40c39a4a249c3f84dc32ce1256e Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 09:36:29 +0000 https://status.langdock.com/#4f642b2085aa153c0f5ce6f856e3758dbec8a12f167f974114af9e25b4b8abba Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 09:33:58 +0000 https://status.langdock.com/#4f642b2085aa153c0f5ce6f856e3758dbec8a12f167f974114af9e25b4b8abba Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 09:28:18 +0000 https://status.langdock.com/#0df48763ec0a76bbfaa0a9c45695b5a3c19a7496866b7826f05c2d7b93b3d5be Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 09:26:38 +0000 https://status.langdock.com/#0df48763ec0a76bbfaa0a9c45695b5a3c19a7496866b7826f05c2d7b93b3d5be Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 09:20:53 +0000 https://status.langdock.com/#643a21f49a988171d52756c5e6c7e146a1641df9d6e226aa2b19aaf876b33ec0 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 09:19:43 +0000 https://status.langdock.com/#643a21f49a988171d52756c5e6c7e146a1641df9d6e226aa2b19aaf876b33ec0 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 09:13:55 +0000 https://status.langdock.com/#55d3778c154348804ece8bd436f825eb8397117d830c180ddc0eecf7e4c790b6 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 09:11:00 +0000 https://status.langdock.com/#55d3778c154348804ece8bd436f825eb8397117d830c180ddc0eecf7e4c790b6 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 09:05:12 +0000 https://status.langdock.com/#bda527a7edeccd0ac7e2b33ca1f8c60d651d4fcc3e34b10b7580f5a9bd8f49ba Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 09:03:43 +0000 https://status.langdock.com/#bda527a7edeccd0ac7e2b33ca1f8c60d651d4fcc3e34b10b7580f5a9bd8f49ba Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 08:52:56 +0000 https://status.langdock.com/#aa61a733593fba69472eadd21dc42a7f3acd4f1a4638f8697fecc74cf1a69e15 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 08:50:48 +0000 https://status.langdock.com/#aa61a733593fba69472eadd21dc42a7f3acd4f1a4638f8697fecc74cf1a69e15 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 08:44:56 +0000 https://status.langdock.com/#049205bd21630e8dcb5fcd21207c4b886449aece5836cf1a7b50003ec276242a Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 08:44:05 +0000 https://status.langdock.com/#049205bd21630e8dcb5fcd21207c4b886449aece5836cf1a7b50003ec276242a Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 08:38:28 +0000 https://status.langdock.com/#1316df250e980e54d87c38824f3784dfe9117f38c51c88559406703f0f770c3a Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 08:37:43 +0000 https://status.langdock.com/#1316df250e980e54d87c38824f3784dfe9117f38c51c88559406703f0f770c3a Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 08:32:00 +0000 https://status.langdock.com/#0e8722bd227be235e8833b74f9cf443054e70f3872d59249bf7e13d9a456cd1c Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 08:31:07 +0000 https://status.langdock.com/#0e8722bd227be235e8833b74f9cf443054e70f3872d59249bf7e13d9a456cd1c Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 08:15:01 +0000 https://status.langdock.com/#9d6cbe83df5813299b6cb2962edca290cb1188b1a27a00fcae20cf3c866167a5 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 08:13:17 +0000 https://status.langdock.com/#9d6cbe83df5813299b6cb2962edca290cb1188b1a27a00fcae20cf3c866167a5 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 08:02:23 +0000 https://status.langdock.com/#3040a7bccf4b567c1ac7ea2fb78dd0187102dbfcbdd87555f0d80df01cb9cf33 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 08:00:32 +0000 https://status.langdock.com/#3040a7bccf4b567c1ac7ea2fb78dd0187102dbfcbdd87555f0d80df01cb9cf33 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 07:54:53 +0000 https://status.langdock.com/#7ea8fd436ef63edfa920f578cad285fd2a46cfe0897063e376ba221e0c5f58c9 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 07:53:44 +0000 https://status.langdock.com/#7ea8fd436ef63edfa920f578cad285fd2a46cfe0897063e376ba221e0c5f58c9 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 07:38:08 +0000 https://status.langdock.com/#24cbd25316dae18d7d1d9e27b95a0d5e8015e26b481797fbd200e00e4bab30c7 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 07:36:39 +0000 https://status.langdock.com/#24cbd25316dae18d7d1d9e27b95a0d5e8015e26b481797fbd200e00e4bab30c7 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 07:25:13 +0000 https://status.langdock.com/#e10e498b4967b38afdc01f24101d6ff1d42a1542119b9b011eb8d85efdd59731 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 07:24:16 +0000 https://status.langdock.com/#e10e498b4967b38afdc01f24101d6ff1d42a1542119b9b011eb8d85efdd59731 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 07:08:48 +0000 https://status.langdock.com/#f9a5042025f9ac513f8e68a2e29c03d1c8827dfbd550b88cb06448c0a694452c Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 07:07:51 +0000 https://status.langdock.com/#f9a5042025f9ac513f8e68a2e29c03d1c8827dfbd550b88cb06448c0a694452c Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 04:04:51 +0000 https://status.langdock.com/#05f2b9bb47fdeead0ce51306b873236ea1248c7f084e41c2fdde9fd453773c69 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 04:04:10 +0000 https://status.langdock.com/#05f2b9bb47fdeead0ce51306b873236ea1248c7f084e41c2fdde9fd453773c69 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 03:31:35 +0000 https://status.langdock.com/#6c956bd20ce8418d9587bdd7467df0617bab72239e91dec7efda8a39a16077b1 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 03:30:40 +0000 https://status.langdock.com/#6c956bd20ce8418d9587bdd7467df0617bab72239e91dec7efda8a39a16077b1 Workflows Runtime went down https://status.langdock.com/ Wed, 10 Jun 2026 03:24:49 +0000 https://status.langdock.com/#4611495f38b41cc2381871b44728d01677148b24840e0f9108bf00f9873dd698 Workflows Runtime recovered https://status.langdock.com/ Wed, 10 Jun 2026 03:23:56 +0000 https://status.langdock.com/#4611495f38b41cc2381871b44728d01677148b24840e0f9108bf00f9873dd698 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 12:28:31 +0000 https://status.langdock.com/#f621edc60faf6b6cac51e6b3e483dae10b20627877fe748f2155179770019d9f Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 12:21:43 +0000 https://status.langdock.com/#f621edc60faf6b6cac51e6b3e483dae10b20627877fe748f2155179770019d9f Workflows Runtime went down https://status.langdock.com/incident/918593 Tue, 09 Jun 2026 07:12:00 -0000 https://status.langdock.com/incident/918593#51500a370493f29c2465eb04464ab61e02497568fa5786583bb6a5b50472c25c The issue is now resolved. File uploads and the workflows runtime should function as expected. https://status.langdock.com/ Tue, 09 Jun 2026 07:05:54 +0000 https://status.langdock.com/#3a50ae4ef00f9f564503202afcfec25de2bec7ad6c3779b5859e6b24127a72f1 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 07:00:17 +0000 https://status.langdock.com/#3a50ae4ef00f9f564503202afcfec25de2bec7ad6c3779b5859e6b24127a72f1 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 06:54:21 +0000 https://status.langdock.com/#4267522a012a4b9e472e26749fdeabb1b1c9b9c497552b1d419540728b865623 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 06:48:34 +0000 https://status.langdock.com/#4267522a012a4b9e472e26749fdeabb1b1c9b9c497552b1d419540728b865623 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 06:13:39 +0000 https://status.langdock.com/#03ac05c24d0f7b7c75ac618cbef706358f5d0a2cbb6db54e3380edd6ffcfbe50 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 06:11:45 +0000 https://status.langdock.com/#03ac05c24d0f7b7c75ac618cbef706358f5d0a2cbb6db54e3380edd6ffcfbe50 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 06:06:14 +0000 https://status.langdock.com/#17a256ace23e6b646f65a3d0d5d45f64a0a1e9e6c90530c8e4656be14b2c812f Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 06:04:08 +0000 https://status.langdock.com/#17a256ace23e6b646f65a3d0d5d45f64a0a1e9e6c90530c8e4656be14b2c812f Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 05:28:52 +0000 https://status.langdock.com/#44d12c0eb525491982dded25629da9adfc0c2d95ea04a480f2b1f52d16988a98 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 05:20:28 +0000 https://status.langdock.com/#44d12c0eb525491982dded25629da9adfc0c2d95ea04a480f2b1f52d16988a98 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 05:14:00 +0000 https://status.langdock.com/#3e4bbe122da8d8cbf37151476cd46694bb0561492d5a4732a923f34fcce07999 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 05:11:25 +0000 https://status.langdock.com/#3e4bbe122da8d8cbf37151476cd46694bb0561492d5a4732a923f34fcce07999 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 04:57:53 +0000 https://status.langdock.com/#40afff04b7eceb8fec429fdbf92279bb7db3bc25f59edaa569af508e822eca42 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 04:44:07 +0000 https://status.langdock.com/#40afff04b7eceb8fec429fdbf92279bb7db3bc25f59edaa569af508e822eca42 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 04:38:21 +0000 https://status.langdock.com/#a37f9289a160d96028578f4117dcc438a7db0b2528214f6ad9b7976059d86403 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 04:35:00 +0000 https://status.langdock.com/#a37f9289a160d96028578f4117dcc438a7db0b2528214f6ad9b7976059d86403 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 04:24:29 +0000 https://status.langdock.com/#78638fa4d12977052dff6638cd04a12acebff36fd4c1b27a858f9f1acb3ce8dc Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 04:21:12 +0000 https://status.langdock.com/#78638fa4d12977052dff6638cd04a12acebff36fd4c1b27a858f9f1acb3ce8dc Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 04:10:48 +0000 https://status.langdock.com/#35859f7d3351476aa17cc7c1ee5d9b702d303e043287d4f54a372a84126170c9 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 04:09:13 +0000 https://status.langdock.com/#35859f7d3351476aa17cc7c1ee5d9b702d303e043287d4f54a372a84126170c9 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 04:03:37 +0000 https://status.langdock.com/#1e04b02d441560b3505b022287ee9015c9752e46c19c1635d084eb3ff10a4635 Workflows Runtime recovered https://status.langdock.com/incident/918593 Tue, 09 Jun 2026 04:02:00 -0000 https://status.langdock.com/incident/918593#85e2649642d75ec0436b34371788779e4852fd79d05c17709861f8cafc2b0b49 File uploads on the Langdock platform are currently slow and some scheduled workflows jobs might be skipped. We're investigating. https://status.langdock.com/ Tue, 09 Jun 2026 03:57:37 +0000 https://status.langdock.com/#1e04b02d441560b3505b022287ee9015c9752e46c19c1635d084eb3ff10a4635 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 03:52:02 +0000 https://status.langdock.com/#967e32b729304c7d6efb2fcb34a1b9a15c431d2fca448ad6769e68d67a8a3867 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 03:49:14 +0000 https://status.langdock.com/#967e32b729304c7d6efb2fcb34a1b9a15c431d2fca448ad6769e68d67a8a3867 Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 03:39:04 +0000 https://status.langdock.com/#df1bb38303bd4ad94b2029b282d8561637b684e8b353c9b07c18615710cfd81f Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 03:35:28 +0000 https://status.langdock.com/#df1bb38303bd4ad94b2029b282d8561637b684e8b353c9b07c18615710cfd81f Workflows Runtime went down https://status.langdock.com/ Tue, 09 Jun 2026 03:03:55 +0000 https://status.langdock.com/#8ff5bbf99ebd21466ee2388886286a36104a9defeb1ca7bd3739eaececf5e112 Workflows Runtime recovered https://status.langdock.com/ Tue, 09 Jun 2026 03:00:10 +0000 https://status.langdock.com/#8ff5bbf99ebd21466ee2388886286a36104a9defeb1ca7bd3739eaececf5e112 Workflows Runtime went down https://status.langdock.com/ Mon, 08 Jun 2026 06:05:25 +0000 https://status.langdock.com/#16380d3dc5ebbd131d4b3e36469bb110bf34e94fe66db5303ca45b6c2e4069d0 Workflows Runtime recovered https://status.langdock.com/ Mon, 08 Jun 2026 06:03:51 +0000 https://status.langdock.com/#16380d3dc5ebbd131d4b3e36469bb110bf34e94fe66db5303ca45b6c2e4069d0 Workflows Runtime went down https://status.langdock.com/ Mon, 08 Jun 2026 01:15:53 +0000 https://status.langdock.com/#128eedf882d1f7f5f17d085d04b71e19ff5597e91d7203d46b0a59a2629ae60e Workflows Runtime recovered https://status.langdock.com/ Mon, 08 Jun 2026 01:14:33 +0000 https://status.langdock.com/#128eedf882d1f7f5f17d085d04b71e19ff5597e91d7203d46b0a59a2629ae60e Workflows Runtime went down https://status.langdock.com/incident/910249 Sat, 06 Jun 2026 20:00:41 -0000 https://status.langdock.com/incident/910249#3e2e3ee8427bd75697da70bce8eca095f940c5b97a46c01e19511455833fcaf8 We're performing planned database maintenance to expand capacity and improve performance. While we've reserved a two-hour window, we expect actual disruption to last only a few minutes, during which Langdock may be briefly unavailable or slower than usual. No data will be affected. We've scheduled this during off-peak hours to minimize disruption. Thank you for your patience! The Langdock Team https://status.langdock.com/ Thu, 04 Jun 2026 02:00:58 +0000 https://status.langdock.com/#a29327821e9c424bab801dd2a7ae089f0660ced803cfc9218898f97b9abab169 app.langdock.com recovered https://status.langdock.com/ Thu, 04 Jun 2026 02:00:57 +0000 https://status.langdock.com/#6e78051cf25065d880dc8f0a1a376582a4ab92260ef4c1a3a6864fd78e592265 Workflows Runtime recovered https://status.langdock.com/ Thu, 04 Jun 2026 02:00:24 +0000 https://status.langdock.com/#6e78051cf25065d880dc8f0a1a376582a4ab92260ef4c1a3a6864fd78e592265 Workflows Runtime went down https://status.langdock.com/ Thu, 04 Jun 2026 01:56:06 +0000 https://status.langdock.com/#a29327821e9c424bab801dd2a7ae089f0660ced803cfc9218898f97b9abab169 app.langdock.com went down https://status.langdock.com/ Mon, 01 Jun 2026 08:23:27 +0000 https://status.langdock.com/#7d164021258c58000cbbbd7d596ef81db82498ef21a4cc5ab311bb8617ebbc6e Workflows Runtime recovered https://status.langdock.com/ Mon, 01 Jun 2026 08:20:36 +0000 https://status.langdock.com/#7d164021258c58000cbbbd7d596ef81db82498ef21a4cc5ab311bb8617ebbc6e Workflows Runtime went down https://status.langdock.com/ Mon, 01 Jun 2026 06:05:11 +0000 https://status.langdock.com/#9f645af8bb46604b7572f00d2186cb45f5e06b0459d4d287124b2ccc6f689fb1 Workflows Runtime recovered https://status.langdock.com/ Mon, 01 Jun 2026 06:03:59 +0000 https://status.langdock.com/#9f645af8bb46604b7572f00d2186cb45f5e06b0459d4d287124b2ccc6f689fb1 Workflows Runtime went down https://status.langdock.com/ Sun, 31 May 2026 04:04:35 +0000 https://status.langdock.com/#fe7c91c95664f06b7171f650eac4d0ce7b355398ddc0deb235cb6e3c3bed8ff5 Workflows Runtime recovered https://status.langdock.com/ Sun, 31 May 2026 04:03:38 +0000 https://status.langdock.com/#fe7c91c95664f06b7171f650eac4d0ce7b355398ddc0deb235cb6e3c3bed8ff5 Workflows Runtime went down https://status.langdock.com/ Sun, 31 May 2026 01:07:56 +0000 https://status.langdock.com/#4acb38dab2312f608c6f2dce924d1a49d860014ff11b58c71b868de0b02a6458 Workflows Runtime recovered https://status.langdock.com/ Sun, 31 May 2026 01:05:41 +0000 https://status.langdock.com/#4acb38dab2312f608c6f2dce924d1a49d860014ff11b58c71b868de0b02a6458 Workflows Runtime went down https://status.langdock.com/ Tue, 26 May 2026 13:21:04 +0000 https://status.langdock.com/#89864d5a8f7d2ab7e3f267c3d6f61d6b82410143732c626384fd036fdb067725 Workflows Runtime recovered https://status.langdock.com/ Tue, 26 May 2026 13:17:06 +0000 https://status.langdock.com/#89864d5a8f7d2ab7e3f267c3d6f61d6b82410143732c626384fd036fdb067725 Workflows Runtime went down https://status.langdock.com/ Tue, 26 May 2026 13:11:23 +0000 https://status.langdock.com/#466578181269beb98582ec28953d53e20770787bc48c982405d911294189732f Workflows Runtime recovered https://status.langdock.com/ Tue, 26 May 2026 13:09:26 +0000 https://status.langdock.com/#466578181269beb98582ec28953d53e20770787bc48c982405d911294189732f Workflows Runtime went down https://status.langdock.com/ Tue, 26 May 2026 13:03:44 +0000 https://status.langdock.com/#5263285097e9f81dbb69725bc509046b908f7caf1123632839cab81a3fb162fa Workflows Runtime recovered https://status.langdock.com/ Tue, 26 May 2026 13:02:50 +0000 https://status.langdock.com/#5263285097e9f81dbb69725bc509046b908f7caf1123632839cab81a3fb162fa Workflows Runtime went down https://status.langdock.com/ Mon, 25 May 2026 16:28:02 +0000 https://status.langdock.com/#61d06cf8b4e9fb7fdfb0970f2df5e96a412c66fb6b83aefc48f380afb68fead9 Workflows Runtime recovered https://status.langdock.com/ Mon, 25 May 2026 16:27:26 +0000 https://status.langdock.com/#61d06cf8b4e9fb7fdfb0970f2df5e96a412c66fb6b83aefc48f380afb68fead9 Workflows Runtime went down https://status.langdock.com/ Mon, 25 May 2026 06:04:59 +0000 https://status.langdock.com/#6f6bb2dfffeda5845a5439df6c1dc15d895403074ddeade826a7d3a59a75e099 Workflows Runtime recovered https://status.langdock.com/ Mon, 25 May 2026 06:04:09 +0000 https://status.langdock.com/#6f6bb2dfffeda5845a5439df6c1dc15d895403074ddeade826a7d3a59a75e099 Workflows Runtime went down https://status.langdock.com/ Tue, 19 May 2026 18:29:58 +0000 https://status.langdock.com/#ab2337b87af1d504d366a27d5b694042b18ba114591a9e9a03f2fffb6f09e5b0 Workflows Runtime recovered https://status.langdock.com/incident/899909 Tue, 19 May 2026 18:28:00 -0000 https://status.langdock.com/incident/899909#7f82021ff46b4ca863e8661982b51317b2f81e8e9d71cdd6868f0e3e35eb7222 The connectivity issues between Langdock and Claude models have been resolved. Service is operating normally again. Thanks for your patience. https://status.langdock.com/ Tue, 19 May 2026 18:00:29 +0000 https://status.langdock.com/#ab2337b87af1d504d366a27d5b694042b18ba114591a9e9a03f2fffb6f09e5b0 Workflows Runtime went down https://status.langdock.com/incident/899909 Tue, 19 May 2026 17:55:00 -0000 https://status.langdock.com/incident/899909#4798e1ef6fef2b0b7ae7b6bddb965c858712971d86785bacaa2120b043f8b9a4 Langdock is currently experiencing intermittent connectivity issues with Claude models. We’re investigating and expect service to stabilize within the next 30 minutes. https://status.langdock.com/ Tue, 19 May 2026 09:42:38 +0000 https://status.langdock.com/#e5be267179c8961c599db7f3dbe9e74c049912733aab269726ec0405c87ff5f1 Workflows Runtime recovered https://status.langdock.com/incident/899530 Tue, 19 May 2026 09:41:00 -0000 https://status.langdock.com/incident/899530#31395c4211db79ef0a2b9035788e22130f8b93d22c02c5149408c8a51489bacc The connectivity issues between Langdock and Claude models have been resolved. Service is operating normally again. Thanks for your patience. https://status.langdock.com/ Tue, 19 May 2026 09:13:09 +0000 https://status.langdock.com/#e5be267179c8961c599db7f3dbe9e74c049912733aab269726ec0405c87ff5f1 Workflows Runtime went down https://status.langdock.com/incident/899530 Tue, 19 May 2026 09:07:00 -0000 https://status.langdock.com/incident/899530#fa5c2690ef557c6d3bd20fa451b11ebbd9dead89c0996d4491a549fabbcb5284 Langdock is currently experiencing intermittent connectivity issues with Claude models. We’re investigating and expect service to stabilize within the next 30 minutes. https://status.langdock.com/incident/889936 Thu, 07 May 2026 05:53:00 -0000 https://status.langdock.com/incident/889936#4aa5558bb63bd236d56ece302e2925515b3ded60eae9332b1c8bc5a9bca2312d File uploads are stable again. However, the daily synchronization of files attached to agents may be delayed. https://status.langdock.com/incident/889936 Thu, 07 May 2026 05:39:00 -0000 https://status.langdock.com/incident/889936#a37d8a2a9bc0e7688834ffa4bbc616c90070ef55f8145c0097bf1f9b3742d9fa Workflows are available again, but workflow executions during the downtime have not run. https://status.langdock.com/ Thu, 07 May 2026 05:38:36 +0000 https://status.langdock.com/#4ffe4de417367b1d3a4c14bf49b4acc7090fa5ed9285ef96aae8f6b0f9dc1c8a Workflows Runtime recovered https://status.langdock.com/ Thu, 07 May 2026 05:36:33 +0000 https://status.langdock.com/#4ffe4de417367b1d3a4c14bf49b4acc7090fa5ed9285ef96aae8f6b0f9dc1c8a Workflows Runtime went down https://status.langdock.com/ Thu, 07 May 2026 05:30:57 +0000 https://status.langdock.com/#aad520d2f5a088c36bb49e8aa83264139a08bc4ac40a9d8e655df8409a05fc6c Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 23:03:07 +0000 https://status.langdock.com/#aad520d2f5a088c36bb49e8aa83264139a08bc4ac40a9d8e655df8409a05fc6c Workflows Runtime went down https://status.langdock.com/incident/889936 Wed, 06 May 2026 23:03:00 -0000 https://status.langdock.com/incident/889936#ff5753bf287aa1bf508ea43affeb003b4ea11d99a3bf6ac9223cd7a0964492af Workflows and file uploads are currently unavailable. Scheduled jobs have not run. We're investigating. https://status.langdock.com/ Wed, 06 May 2026 18:02:43 +0000 https://status.langdock.com/#a756b65761bf2c67d8f7bc4d47b09d802b090ec7ca2e6bc3b111b5a2eda57bee Workflows Runtime recovered https://status.langdock.com/incident/889503 Wed, 06 May 2026 18:00:00 -0000 https://status.langdock.com/incident/889503#9f2474de9de4b822504a37b4bf39659e0e65152e6053f83ae8b78cd9d1b4d916 The issue has been resolved. https://status.langdock.com/ Wed, 06 May 2026 17:31:02 +0000 https://status.langdock.com/#a756b65761bf2c67d8f7bc4d47b09d802b090ec7ca2e6bc3b111b5a2eda57bee Workflows Runtime went down https://status.langdock.com/incident/889503 Wed, 06 May 2026 17:28:00 -0000 https://status.langdock.com/incident/889503#874feb6e4b2e53a6814ba766b00325684bf56ee68145deb643df80d5af34162a We have identified the issue and have released a fix. We are still observing higher issue rates with some models (mainly Claude) models and continue to investigate. https://status.langdock.com/incident/889503 Wed, 06 May 2026 17:12:00 -0000 https://status.langdock.com/incident/889503#61f7848b065cab583820c6ffbc63de2bc76e54a3990dbb1e22a2e79c8cb5cd29 We are observing issues with LLM answer generations and conversations not loading. We are investigating. https://status.langdock.com/incident/889184 Wed, 06 May 2026 12:28:00 -0000 https://status.langdock.com/incident/889184#0671988195a9e881acd8ca7e1dcadfe4e4cf573c422827744fa15a7a154bf49f All issues have been resolved. Platform speed, loading of old chats, Claude models, and connections to Google integrations are stable again. Thanks for your patience. https://status.langdock.com/ Wed, 06 May 2026 12:25:29 +0000 https://status.langdock.com/#c7568566686d09bdbc929e80114cc33453aa569b8ca8567d357fb30298ca8da6 Workflows Runtime recovered https://status.langdock.com/incident/889184 Wed, 06 May 2026 12:07:00 -0000 https://status.langdock.com/incident/889184#d1d7851e2e1562fcfad5d7f70137aae50605e681eec2da18d5b9945b64aab0fb The loading of old chats and general response time issue has been fixed, and the platform is stable again. We’re continuing to investigate an issue causing instability with some Claude models and Google service integrations. We expect to resolve this within the next half hour. https://status.langdock.com/ Wed, 06 May 2026 11:56:41 +0000 https://status.langdock.com/#c7568566686d09bdbc929e80114cc33453aa569b8ca8567d357fb30298ca8da6 Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 11:51:01 +0000 https://status.langdock.com/#3cb08ee01a5fadf660578ac004a891f3364bbbfcb17e979138faf844043aa732 Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 11:49:06 +0000 https://status.langdock.com/#3cb08ee01a5fadf660578ac004a891f3364bbbfcb17e979138faf844043aa732 Workflows Runtime went down https://status.langdock.com/incident/889184 Wed, 06 May 2026 11:45:00 -0000 https://status.langdock.com/incident/889184#1db08037609574f4ca3baefe0ad33994937a7da17c3e16c0b4e239b194c6816a Currently, old chats can’t be accessed, and in some cases, the AI responses are slow. We have already identified the issue and are actively working on a fix. https://status.langdock.com/ Wed, 06 May 2026 11:32:15 +0000 https://status.langdock.com/#fc482aea214c49d55cc2cbe7d2ed786740fd4ddd01cdbd5f5918cc558ddae599 Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 11:30:17 +0000 https://status.langdock.com/#fc482aea214c49d55cc2cbe7d2ed786740fd4ddd01cdbd5f5918cc558ddae599 Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 10:56:08 +0000 https://status.langdock.com/#fc7b50bc9956cc655bd81ff880c1fd930bbd9fe7691f8a1fa4f4680fa06e4d6e Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 10:55:37 +0000 https://status.langdock.com/#fc7b50bc9956cc655bd81ff880c1fd930bbd9fe7691f8a1fa4f4680fa06e4d6e Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 10:21:41 +0000 https://status.langdock.com/#7edbd06f5e42eacffdd1fd25330f7e69d6a31c3c95a610f6ab19edbfdcee5eb7 Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 10:21:11 +0000 https://status.langdock.com/#7edbd06f5e42eacffdd1fd25330f7e69d6a31c3c95a610f6ab19edbfdcee5eb7 Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 10:03:52 +0000 https://status.langdock.com/#963e81b88cfb47e0e82b961b77c76dda8ad45487e09e1bce02e5f8174e2c7b98 Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 10:02:53 +0000 https://status.langdock.com/#963e81b88cfb47e0e82b961b77c76dda8ad45487e09e1bce02e5f8174e2c7b98 Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 09:45:56 +0000 https://status.langdock.com/#727be1a18d8622ea2e8a915cc9d520df90406595f47ed71a8d00fd099d50e2e7 Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 09:44:18 +0000 https://status.langdock.com/#727be1a18d8622ea2e8a915cc9d520df90406595f47ed71a8d00fd099d50e2e7 Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 09:38:25 +0000 https://status.langdock.com/#7c6ae4a6b20919d11694f546f9e1f67dab87a083051f44589841a5b33cc20e9c Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 09:36:37 +0000 https://status.langdock.com/#7c6ae4a6b20919d11694f546f9e1f67dab87a083051f44589841a5b33cc20e9c Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 09:25:33 +0000 https://status.langdock.com/#3b3dadac07f633ae0628c572bb1185fe4125bda478400eb116cfef1330d4f46f Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 09:24:43 +0000 https://status.langdock.com/#3b3dadac07f633ae0628c572bb1185fe4125bda478400eb116cfef1330d4f46f Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 09:19:03 +0000 https://status.langdock.com/#40924b66ec35d2ca8d8fc16ae36746c42ee0f5957f68748d58ec89e927d5029b Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 09:17:50 +0000 https://status.langdock.com/#40924b66ec35d2ca8d8fc16ae36746c42ee0f5957f68748d58ec89e927d5029b Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 09:02:15 +0000 https://status.langdock.com/#4f5cad360c7d19d93502ef384a3daf979d8d797564841b7a97961b4ca0d7eb48 Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 08:59:59 +0000 https://status.langdock.com/#4f5cad360c7d19d93502ef384a3daf979d8d797564841b7a97961b4ca0d7eb48 Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 08:48:25 +0000 https://status.langdock.com/#dfbaf66dfa6dc7f91f43e75d8a6191283503a7a0d13cf576930e77e53b382bac Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 08:47:37 +0000 https://status.langdock.com/#dfbaf66dfa6dc7f91f43e75d8a6191283503a7a0d13cf576930e77e53b382bac Workflows Runtime went down https://status.langdock.com/ Wed, 06 May 2026 08:37:14 +0000 https://status.langdock.com/#a0fc70a144efe62f83fb1d5b4efe0da671f0ac83ccde81cb5b31d911a6e21363 Workflows Runtime recovered https://status.langdock.com/ Wed, 06 May 2026 08:36:42 +0000 https://status.langdock.com/#a0fc70a144efe62f83fb1d5b4efe0da671f0ac83ccde81cb5b31d911a6e21363 Workflows Runtime went down https://status.langdock.com/ Fri, 01 May 2026 06:05:46 +0000 https://status.langdock.com/#41832ef8107a439b288e8dbe4557925eabea5a5fd524517d39596635d04ffe98 Workflows Runtime recovered https://status.langdock.com/ Fri, 01 May 2026 01:41:33 +0000 https://status.langdock.com/#41832ef8107a439b288e8dbe4557925eabea5a5fd524517d39596635d04ffe98 Workflows Runtime went down https://status.langdock.com/ Fri, 01 May 2026 01:35:46 +0000 https://status.langdock.com/#834f02861a39f56be69f150de58732a1817d8f4638c9d18dca7a21652c12f405 Workflows Runtime recovered https://status.langdock.com/ Fri, 01 May 2026 01:35:05 +0000 https://status.langdock.com/#834f02861a39f56be69f150de58732a1817d8f4638c9d18dca7a21652c12f405 Workflows Runtime went down https://status.langdock.com/ Wed, 29 Apr 2026 18:08:05 +0000 https://status.langdock.com/#99fbd24cadfe247dade497ae67678803c026714a8ac78e304715acc6db14c9f8 Workflows Runtime recovered https://status.langdock.com/ Wed, 29 Apr 2026 17:40:15 +0000 https://status.langdock.com/#99fbd24cadfe247dade497ae67678803c026714a8ac78e304715acc6db14c9f8 Workflows Runtime went down https://status.langdock.com/incident/881181 Mon, 27 Apr 2026 18:51:00 -0000 https://status.langdock.com/incident/881181#e8e1a712dde1a3434aaf11980dd62ea42a11ff01572b797ef7dab3e34c8d028b We have identified the root cause and fixed the issue. We experienced a failed database migration which caused some services not to start correctly. Langdock is available again for all users. We will continue to monitor the situation. https://status.langdock.com/incident/881181 Mon, 27 Apr 2026 18:30:00 -0000 https://status.langdock.com/incident/881181#51357879e2c4014c60a95ca1e9526d4d8c1fc1d9abbb288190cedce59baec68e 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, 23 Apr 2026 14:23:11 +0000 https://status.langdock.com/#a9ec9a2e78f180bb1f491f428647caf0441f9350d59bd7df669f4f202fe8e3ca Workflows Runtime recovered https://status.langdock.com/ Thu, 23 Apr 2026 13:56:12 +0000 https://status.langdock.com/#a9ec9a2e78f180bb1f491f428647caf0441f9350d59bd7df669f4f202fe8e3ca Workflows Runtime went down https://status.langdock.com/ Thu, 23 Apr 2026 09:11:25 +0000 https://status.langdock.com/#e5bd832daf28f9d701f51bf2798967e2700e49f327552a10fb0307458325fab4 Workflows Runtime recovered https://status.langdock.com/ Thu, 23 Apr 2026 08:44:21 +0000 https://status.langdock.com/#e5bd832daf28f9d701f51bf2798967e2700e49f327552a10fb0307458325fab4 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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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.