- Detected by Pingoru
- Jun 10, 2026, 01:49 PM UTC
- Resolved
- Jun 10, 2026, 01:49 PM UTC
- Duration
- —
Affected: LangSmith APILangSmith Application
Timeline · 3 updates
-
investigating Jun 10, 2026, 12:41 PM UTC
Status: Investigating We are experiencing a performance degradation in one of our legacy storage clusters after a recent version update. This could lead to timeouts when querying trace information. Work is underway to revert the update. Ingestion of trace data is not impacted. Affected components LangSmith API (Degraded performance) LangSmith Application (Degraded performance)
-
monitoring Jun 10, 2026, 01:39 PM UTC
Status: Monitoring The rollback of the legacy storage cluster is mostly complete, and request latencies have largely normalized. Affected components LangSmith API (Degraded performance) LangSmith Application (Degraded performance)
-
resolved Jun 10, 2026, 01:49 PM UTC
Status: Resolved The rollback is complete, and our latency readings are back to nominal levels. Affected components LangSmith API (Operational) LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 07, 2026, 10:08 AM UTC
- Resolved
- Jun 07, 2026, 10:08 AM UTC
- Duration
- —
Affected: LangSmith APILangSmith Application
Timeline · 3 updates
-
investigating Jun 07, 2026, 09:50 AM UTC
Status: Investigating We are investigating elevated error rates in the LangSmith API. Affected components LangSmith API (Partial outage) LangSmith Application (Partial outage)
-
monitoring Jun 07, 2026, 09:54 AM UTC
Status: Monitoring We've mitigated the issue and are seeing initial recovery and are continuing to monitor. Affected components LangSmith API (Operational) LangSmith Application (Operational)
-
resolved Jun 07, 2026, 10:08 AM UTC
Status: Resolved This incident has been resolved. Affected components LangSmith API (Operational) LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2026, 02:08 AM UTC
- Resolved
- Jun 06, 2026, 02:08 AM UTC
- Duration
- —
Affected: LangSmith Billing
Timeline · 3 updates
-
identified Jun 05, 2026, 06:38 PM UTC
Status: Identified We have identified an issue causing delays in billable usage tracking for LangSmith Deployments. Affected components LangSmith Billing (Degraded performance)
-
monitoring Jun 06, 2026, 12:23 AM UTC
Status: Monitoring We have a fix in place and are processing the backlog of usage. Affected components LangSmith Billing (Degraded performance)
-
resolved Jun 06, 2026, 02:08 AM UTC
Status: Resolved The backlog has completed processing. This incident is resolved. Affected components LangSmith Billing (Operational)
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 03:38 PM UTC
- Resolved
- May 27, 2026, 03:38 PM UTC
- Duration
- —
Affected: LangSmith API
Timeline · 3 updates
-
investigating May 27, 2026, 12:09 PM UTC
Status: Investigating We're currently investigating an issue causing a number of bulk exports to become stuck. Affected components LangSmith API (Partial outage)
-
monitoring May 27, 2026, 01:32 PM UTC
Status: Monitoring A fix has been successfully deployed and bulk exports are succeeding again. The team continue to monitor for any further issues. Affected components LangSmith API (Operational)
-
resolved May 27, 2026, 03:38 PM UTC
Status: Resolved No further issues have been observed and this incident is now considered resolved. Affected components LangSmith API (Operational)
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 05:29 PM UTC
- Resolved
- May 22, 2026, 05:29 PM UTC
- Duration
- —
Affected: LangSmith Sandboxes
Timeline · 4 updates
-
investigating May 22, 2026, 04:35 PM UTC
Status: Investigating All sandbox create calls error Affected components LangSmith Sandboxes (Partial outage)
-
identified May 22, 2026, 05:15 PM UTC
Status: Identified Fix is rolling out Affected components LangSmith Sandboxes (Partial outage)
-
monitoring May 22, 2026, 05:16 PM UTC
Status: Monitoring Creates succeeding again Affected components LangSmith Sandboxes (Operational)
-
resolved May 22, 2026, 05:29 PM UTC
Status: Resolved Resolved Affected components LangSmith Sandboxes (Operational)
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 12:38 AM UTC
- Resolved
- May 16, 2026, 12:38 AM UTC
- Duration
- —
Affected: LangSmith API
Timeline · 5 updates
-
investigating May 14, 2026, 04:53 PM UTC
Status: Investigating We're currently investigating an issue causing some bulk exports to fail or become stuck. Affected components LangSmith API (Partial outage)
-
identified May 15, 2026, 01:27 AM UTC
Status: Identified The team have identified the issue and a fix is being deployed. Affected components LangSmith API (Partial outage)
-
monitoring May 15, 2026, 02:51 AM UTC
Status: Monitoring The fix has been successfully deployed and bulk exports are succeeding again. The team continue to monitor for any further issues. Affected components LangSmith API (Operational)
-
investigating May 15, 2026, 01:55 PM UTC
Status: Investigating Unfortunately we continue to see a number of bulk export jobs failing. The team are investigating the cause. Affected components LangSmith API (Partial outage)
-
resolved May 16, 2026, 12:38 AM UTC
Status: Resolved This incident has been resolved. Affected components LangSmith API (Operational)
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 02:00 PM UTC
- Resolved
- May 13, 2026, 02:00 PM UTC
- Duration
- —
Affected: LangSmith Run IngestionLangSmith APILangSmith Application
Timeline · 3 updates
-
investigating May 13, 2026, 12:58 PM UTC
Status: Investigating We are investigating an increase in backend latency in the LangSmith service. Affected components LangSmith API (Degraded performance) LangSmith Run Ingestion (Degraded performance) LangSmith Application (Degraded performance)
-
identified May 13, 2026, 01:44 PM UTC
Status: Identified We identified a database modification that came through our regular release pipeline and caused backend contention, resulting in overall slowness in our API and WebUI. Affected components LangSmith API (Degraded performance) LangSmith Run Ingestion (Degraded performance) LangSmith Application (Degraded performance)
-
resolved May 13, 2026, 02:00 PM UTC
Status: Resolved The issue is now fully resolved. All services are restored and fully operational. Affected components LangSmith API (Operational) LangSmith Run Ingestion (Operational) LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 06:30 PM UTC
- Resolved
- Apr 30, 2026, 06:30 PM UTC
- Duration
- —
Affected: LangSmith Application
Timeline · 4 updates
-
investigating Apr 30, 2026, 02:59 PM UTC
Status: Investigating We're currently investigating an incident affecting trace visualization in the LangSmith UI. Traces may not render correctly or may fail to load. Affected components LangSmith Application (Partial outage)
-
identified Apr 30, 2026, 03:33 PM UTC
Status: Identified We have identified the root cause and are working on a fix. Affected components LangSmith Application (Partial outage)
-
monitoring Apr 30, 2026, 04:19 PM UTC
Status: Monitoring We have deployed a fix and are continuing to monitor the situation closely. Trace ingestion was not impacted. We apologize for the inconvenience. Affected components LangSmith Application (Partial outage)
-
resolved Apr 30, 2026, 06:30 PM UTC
Status: Resolved The fix has been properly released. Thank you for your patience and sorry for the inconvenience. Affected components LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 02:25 PM UTC
- Resolved
- Apr 28, 2026, 02:25 PM UTC
- Duration
- —
Affected: LangSmith Application
Timeline · 3 updates
-
investigating Apr 28, 2026, 08:44 AM UTC
Status: Investigating We're investigating an issue where the annotation queue page may load very slowly or even freeze the UI after clicking the View Run button. Affected components LangSmith Application (Degraded performance)
-
identified Apr 28, 2026, 11:25 AM UTC
Status: Identified The cause of the issue has been identified and the team is currently working on a fix. Affected components LangSmith Application (Degraded performance)
-
resolved Apr 28, 2026, 02:25 PM UTC
Status: Resolved This incident has been resolved. Annotation queues are once again fully accessible in the US LangSmith UI. Please let us know at [email protected] if you're still experiencing issues. Affected components LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 02:11 PM UTC
- Resolved
- Mar 16, 2026, 02:11 PM UTC
- Duration
- —
Affected: LangSmith Deployments Data PlaneLangSmith Deployments Control Plane
Timeline · 4 updates
-
investigating Mar 16, 2026, 10:02 AM UTC
Status: Investigating We're currently investigating an issue causing deployment failures. Affected components LangSmith Deployments Data Plane (Partial outage)
-
identified Mar 16, 2026, 10:41 AM UTC
Status: Identified The issue is impacting the LangSmith Deployments Control Plane. A fix is being deployed now. Affected components LangSmith Deployments Control Plane (Partial outage) LangSmith Deployments Data Plane (Operational)
-
monitoring Mar 16, 2026, 10:47 AM UTC
Status: Monitoring A fix for this issue has been deployed. The team continue to monitor system health. Affected components LangSmith Deployments Control Plane (Operational) LangSmith Deployments Data Plane (Operational)
-
resolved Mar 16, 2026, 02:11 PM UTC
Status: Resolved The fix was successful and this issue is now considered resolved. Affected components LangSmith Deployments Control Plane (Operational) LangSmith Deployments Data Plane (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 03:14 AM UTC
- Resolved
- Feb 27, 2026, 03:14 AM UTC
- Duration
- —
Affected: LangSmith API
Timeline · 4 updates
-
identified Feb 26, 2026, 06:12 PM UTC
Status: Identified We've identified a capacity issue causing stuck and delayed bulk exports. We're working on increasing capacity to mitigate. Affected components LangSmith API (Degraded performance)
-
identified Feb 26, 2026, 08:24 PM UTC
Status: Identified We've scaled up the relevant systems and are observing recovery as the queue drains. Affected components LangSmith API (Degraded performance)
-
monitoring Feb 26, 2026, 10:58 PM UTC
Status: Monitoring The backlog is continuing to process, and we are continuing to monitor. Affected components LangSmith API (Degraded performance)
-
resolved Feb 27, 2026, 03:14 AM UTC
Status: Resolved This incident has been resolved. Affected components LangSmith API (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 12:28 AM UTC
- Resolved
- Feb 23, 2026, 12:28 AM UTC
- Duration
- —
Affected: LangSmith Run IngestionLangSmith BillingLangSmith PromptHubLangSmith APILangSmith ApplicationLangSmith Deployments Control Plane
Timeline · 3 updates
-
monitoring Feb 22, 2026, 12:05 AM UTC
Status: Monitoring We have just experienced a ~18 minute period between 3:24-3:42PM PDT of elevated 5XX error rates impacting all endpoints including trace ingestion. Our systems have recovered and we are monitoring closely. Affected components LangSmith Application (Partial outage) LangSmith Deployments Control Plane (Partial outage) LangSmith Billing (Partial outage) LangSmith PromptHub (Partial outage) LangSmith API (Partial outage) LangSmith Run Ingestion (Partial outage)
-
monitoring Feb 22, 2026, 12:06 AM UTC
Status: Monitoring Systems are operational, and we are monitoring closely. Affected components LangSmith Deployments Control Plane (Operational) LangSmith Billing (Operational) LangSmith PromptHub (Operational) LangSmith API (Operational) LangSmith Run Ingestion (Operational) LangSmith Application (Operational)
-
resolved Feb 23, 2026, 12:28 AM UTC
Status: Resolved All services were restored and fully operational on February 21, 2026, at 23:42 UTC. Affected components LangSmith Deployments Control Plane (Operational) LangSmith Billing (Operational) LangSmith PromptHub (Operational) LangSmith API (Operational) LangSmith Run Ingestion (Operational) LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 07:33 PM UTC
- Resolved
- Feb 21, 2026, 07:33 PM UTC
- Duration
- —
Affected: LangSmith Application
Timeline · 3 updates
-
investigating Feb 21, 2026, 05:17 PM UTC
Status: Investigating Impact limited to stats and no impact to trace ingestion or other capabilities. Our engineers are working with our service provider to address the cause Affected components LangSmith Application (Degraded performance)
-
monitoring Feb 21, 2026, 05:53 PM UTC
Status: Monitoring Services are recovering. We are monitoring to ensure normal operations Affected components LangSmith Application (Degraded performance)
-
resolved Feb 21, 2026, 07:33 PM UTC
Status: Resolved All services are back to normal operations Affected components LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 05:17 PM UTC
- Resolved
- Feb 21, 2026, 07:33 PM UTC
- Duration
- 2h 16m
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 09:20 PM UTC
- Resolved
- Feb 19, 2026, 09:20 PM UTC
- Duration
- —
Affected: LangSmith Deployments Data Plane
Timeline · 4 updates
-
investigating Feb 17, 2026, 09:12 PM UTC
Status: Investigating All deployments in the us-central region are currently down. Affected components LangSmith Deployments Data Plane (Partial outage)
-
identified Feb 17, 2026, 10:22 PM UTC
Status: Identified Fix is in progress, deployments should be back up shortly. Affected components LangSmith Deployments Data Plane (Partial outage)
-
monitoring Feb 17, 2026, 11:04 PM UTC
Status: Monitoring All deployments in the us-central region have been restored, currently monitoring the health of the cluster to verify no degradation. Affected components LangSmith Deployments Data Plane (Partial outage)
-
resolved Feb 19, 2026, 09:20 PM UTC
Status: Resolved LangSmith Deployments us-central cluster is now fully operational. Affected components LangSmith Deployments Data Plane (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 02:04 PM UTC
- Resolved
- Feb 04, 2026, 02:04 PM UTC
- Duration
- —
Affected: LangSmith APILangSmith Application
Timeline · 4 updates
-
investigating Feb 04, 2026, 12:17 PM UTC
Status: Investigating We are currently investigating an issue where some users are seeing 0 examples or incomplete data within their datasets. Our preliminary investigation suggests this is a display and query issue rather than a loss of underlying data. What this means for you: • You may see "0 examples" on datasets that previously contained data. • API calls for these datasets may return incomplete results, which can impact active evaluations and experiments. Current Status: We are currently working on a fix to restore full visibility to all affected datasets. No data has been deleted, and we are working to ensure all examples are visible again as soon as possible. Affected components LangSmith API (Degraded performance) LangSmith Application (Degraded performance)
-
identified Feb 04, 2026, 01:28 PM UTC
Status: Identified We have identified the root cause of an issue affecting dataset visibility and are working on a fix. No data loss has occurred. We will provide another update shortly. Affected components LangSmith API (Degraded performance) LangSmith Application (Degraded performance)
-
monitoring Feb 04, 2026, 01:50 PM UTC
Status: Monitoring A fix has been deployed to restore dataset visibility. We are currently monitoring the system to ensure all data is appearing correctly across the platform. Affected components LangSmith API (Degraded performance) LangSmith Application (Degraded performance)
-
resolved Feb 04, 2026, 02:04 PM UTC
Status: Resolved Issue has been identified as only having affecting EU customers. No impact on US customers. Affected components LangSmith API (Operational) LangSmith Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Dec 27, 2025, 04:16 AM UTC
- Resolved
- Jan 05, 2026, 08:07 PM UTC
- Duration
- 9d 15h
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 11:45 PM UTC
- Resolved
- Dec 22, 2025, 02:09 PM UTC
- Duration
- 4d 14h
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 12:23 AM UTC
- Resolved
- Dec 17, 2025, 12:40 AM UTC
- Duration
- 16m
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 11:26 AM UTC
- Resolved
- Dec 04, 2025, 03:38 AM UTC
- Duration
- 1d 16h
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 06:34 PM UTC
- Resolved
- Nov 19, 2025, 02:55 AM UTC
- Duration
- 8h 21m
Read the full incident report →
Critical November 14, 2025 - Detected by Pingoru
- Nov 14, 2025, 04:30 PM UTC
- Resolved
- Nov 14, 2025, 11:46 PM UTC
- Duration
- 7h 15m
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2025, 02:49 PM UTC
- Resolved
- Oct 06, 2025, 07:21 PM UTC
- Duration
- 4h 32m
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2025, 06:22 PM UTC
- Resolved
- Sep 26, 2025, 04:54 PM UTC
- Duration
- 22h 32m
Read the full incident report →
Critical September 24, 2025 - Detected by Pingoru
- Sep 24, 2025, 11:43 PM UTC
- Resolved
- Sep 25, 2025, 02:36 AM UTC
- Duration
- 2h 52m
Read the full incident report →