Incidents | LangWatch Incidents reported on status page for LangWatch https://status.langwatch.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/9165bc0fa7d9e1ef8c561df85138d57f.png Incidents | LangWatch https://status.langwatch.ai/ en Processor recovered https://status.langwatch.ai/ Mon, 01 Dec 2025 17:11:07 +0000 https://status.langwatch.ai/#47b040ebc3d18c6aca963965ba14779e73e4b5735fb48ae6ec6b698a49e7387d Processor recovered Collector recovered https://status.langwatch.ai/ Mon, 01 Dec 2025 17:09:26 +0000 https://status.langwatch.ai/#5ea4af6dacdcec96bf5a5ffcbf1bd5e492e22bcd8e001a8bd29df84ffb066bdc Collector recovered Collector went down https://status.langwatch.ai/ Mon, 01 Dec 2025 16:39:23 +0000 https://status.langwatch.ai/#5ea4af6dacdcec96bf5a5ffcbf1bd5e492e22bcd8e001a8bd29df84ffb066bdc Collector went down Processor went down https://status.langwatch.ai/ Mon, 01 Dec 2025 16:36:54 +0000 https://status.langwatch.ai/#47b040ebc3d18c6aca963965ba14779e73e4b5735fb48ae6ec6b698a49e7387d Processor went down Triggers recovered https://status.langwatch.ai/ Sat, 29 Nov 2025 15:13:55 +0000 https://status.langwatch.ai/#ede3b2448acf5c1365383b89f643d353d9a42006654190fd020199031d4d82ef Triggers recovered Triggers went down https://status.langwatch.ai/ Sat, 29 Nov 2025 12:02:26 +0000 https://status.langwatch.ai/#ede3b2448acf5c1365383b89f643d353d9a42006654190fd020199031d4d82ef Triggers went down Processor recovered https://status.langwatch.ai/ Fri, 28 Nov 2025 00:15:33 +0000 https://status.langwatch.ai/#4b0007c09e77d7f7d122d5c637503e1e021f712fde2e1d405889e7643aa93218 Processor recovered Processor went down https://status.langwatch.ai/ Fri, 28 Nov 2025 00:01:24 +0000 https://status.langwatch.ai/#4b0007c09e77d7f7d122d5c637503e1e021f712fde2e1d405889e7643aa93218 Processor went down Collector recovered https://status.langwatch.ai/ Tue, 18 Nov 2025 12:41:42 +0000 https://status.langwatch.ai/#56cd5504a5f10309587c6910dc347ed045bf34713eca6e2c30b1e3a7e6d4be5c Collector recovered Processor recovered https://status.langwatch.ai/ Tue, 18 Nov 2025 12:40:51 +0000 https://status.langwatch.ai/#723ab529e677433110655a2c9b5a84759dfef0a91db6c15f0e6b67bb30dfcc79 Processor recovered Processor went down https://status.langwatch.ai/ Tue, 18 Nov 2025 11:42:19 +0000 https://status.langwatch.ai/#723ab529e677433110655a2c9b5a84759dfef0a91db6c15f0e6b67bb30dfcc79 Processor went down Collector went down https://status.langwatch.ai/ Tue, 18 Nov 2025 11:41:54 +0000 https://status.langwatch.ai/#56cd5504a5f10309587c6910dc347ed045bf34713eca6e2c30b1e3a7e6d4be5c Collector went down Processor recovered https://status.langwatch.ai/ Wed, 12 Nov 2025 14:42:13 +0000 https://status.langwatch.ai/#6569f772fdca78eb0c18c62a7747403f59dacab8bd2933d56d7e18a5c676f2e4 Processor recovered Collector recovered https://status.langwatch.ai/ Wed, 12 Nov 2025 14:40:31 +0000 https://status.langwatch.ai/#f1e1d72424589bc1c8822b4428ea4f03f136d11e9c290e0bf1c32336d712473c Collector recovered Collector went down https://status.langwatch.ai/ Wed, 12 Nov 2025 14:24:38 +0000 https://status.langwatch.ai/#f1e1d72424589bc1c8822b4428ea4f03f136d11e9c290e0bf1c32336d712473c Collector went down Processor went down https://status.langwatch.ai/ Wed, 12 Nov 2025 14:24:07 +0000 https://status.langwatch.ai/#6569f772fdca78eb0c18c62a7747403f59dacab8bd2933d56d7e18a5c676f2e4 Processor went down Primary Trace Storage Down https://status.langwatch.ai/incident/548080 Sun, 20 Apr 2025 12:19:00 -0000 https://status.langwatch.ai/incident/548080#12d8b1874b63107d16d309cb5806fd48962d9bee424ad24d22cb1bb11efce268 All services back up Primary Trace Storage Down https://status.langwatch.ai/incident/548080 Sun, 20 Apr 2025 12:19:00 -0000 https://status.langwatch.ai/incident/548080#12d8b1874b63107d16d309cb5806fd48962d9bee424ad24d22cb1bb11efce268 All services back up Primary Trace Storage Down https://status.langwatch.ai/incident/548080 Sun, 20 Apr 2025 12:17:00 -0000 https://status.langwatch.ai/incident/548080#8258c451cf0715dc122a90cb48fd2c04d34b987ae61e3776bb3f4b669f82a88e Our primary Elasticsearch Nodes became unresponsive on Sunday Apr 4, 3:03 AM on Elastic Cloud with unexpected no possibility of recovery, causing an outage on monitoring services and triggers in LangWatch and the messages display on the dashboard. A forced data migration to a new cluster throughout the morning was necessary to bring services back up. Workflows and Evaluations remained unaffected. Primary Trace Storage Down https://status.langwatch.ai/incident/548080 Sun, 20 Apr 2025 12:17:00 -0000 https://status.langwatch.ai/incident/548080#8258c451cf0715dc122a90cb48fd2c04d34b987ae61e3776bb3f4b669f82a88e Our primary Elasticsearch Nodes became unresponsive on Sunday Apr 4, 3:03 AM on Elastic Cloud with unexpected no possibility of recovery, causing an outage on monitoring services and triggers in LangWatch and the messages display on the dashboard. A forced data migration to a new cluster throughout the morning was necessary to bring services back up. Workflows and Evaluations remained unaffected. Workflows Infra Upgrade https://status.langwatch.ai/incident/514957 Tue, 18 Feb 2025 17:00:00 -0000 https://status.langwatch.ai/incident/514957#de0a9b5f60241dd6ddd20e1c9aada96ec6d74a3f3106bc84cf134b7532d389cf Maintenance completed Workflows Infra Upgrade https://status.langwatch.ai/incident/514957 Tue, 18 Feb 2025 16:00:00 -0000 https://status.langwatch.ai/incident/514957#88468ee390be783655c46f339594da3ed0b5862fc4a67275c33bde1f4e603291 Workflows might be intermittently not available during the period