Is LangSmith down? › Outage history › Aug 6, 2026
LangSmith partial outage on Aug 6, 2026: what happened
On Aug 6, 2026, the LangSmith Global status page reported "Partial ingestion failures for traces with large payloads". About 16 hours 37 min: from Aug 6, 2026, 15:03 UTC to Aug 7, 2026, 07:40 UTC, by the official start and resolution times.
LangSmith right now
At our last refresh (Oct 22, 2026, 12:35 UTC) LangSmith was having problems: Partial System Degradation.
- Started
- Aug 6, 2026, 15:03 UTC
- Resolved
- Aug 7, 2026, 07:40 UTC
- Duration
- 16 hours 37 min
- Official impact
- Major
- Source
- Partial ingestion failures for traces with large payloads on the LangSmith Global status page
The LangSmith Global status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
What caused the LangSmith partial outage?
"The full fix took an extraordinarily long time to release due to an outage at our CI provider."
From the LangSmith Global status page, Aug 7, 2026, 07:40 UTC.
When was it fixed?
The LangSmith Global status page marked it resolved at Aug 7, 2026, 07:40 UTC, 16 hours 37 min after it started. A fix was in place and being monitored from Aug 6, 2026, 16:43 UTC. Its resolution note: "The full fix took an extraordinarily long time to release due to an outage at our CI provider. In the meantime, the mitigation we had deployed mitigated the problem."
Timeline of official updates
Every update the LangSmith Global status page posted, oldest first. Times are UTC.
Aug 6, 2026, 15:03 UTC identified
Traces including large payloads might currently fail to be ingested or can be delayed. We are working on a fix.
Aug 6, 2026, 15:33 UTC identified
Updated affected regions
Aug 6, 2026, 16:43 UTC monitoring
The service is temporarily patched. Large payloads are now ingested normally.
Aug 7, 2026, 07:40 UTC resolved
The full fix took an extraordinarily long time to release due to an outage at our CI provider. In the meantime, the mitigation we had deployed mitigated the problem.
LangSmith partial outage questions
What caused the LangSmith partial outage on Aug 6, 2026?
The LangSmith Global status page said (update at Aug 7, 2026, 07:40 UTC): "The full fix took an extraordinarily long time to release due to an outage at our CI provider."
When was the LangSmith partial outage on Aug 6, 2026 fixed?
The LangSmith Global status page marked it resolved at Aug 7, 2026, 07:40 UTC, 16 hours 37 min after it started. A fix was in place and being monitored from Aug 6, 2026, 16:43 UTC. Its resolution note: "The full fix took an extraordinarily long time to release due to an outage at our CI provider. In the meantime, the mitigation we had deployed mitigated the problem."
How long did the LangSmith partial outage last?
About 16 hours 37 min: from Aug 6, 2026, 15:03 UTC to Aug 7, 2026, 07:40 UTC, by the official start and resolution times.
Was LangSmith completely down?
No. The LangSmith Global status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
Other recent LangSmith incidents
- Sandbox Performance Degraded Oct 14, 2026, 19:47 UTC, ongoing, 7 days 17 hours so far
- APAC Region Querying is down Oct 12, 2026, 06:46 UTC, duration not stated
- Seeing some issues logging into the application Oct 12, 2026, 05:42 UTC, 2 days 10 hours
- LLM Gateway service interruption Oct 8, 2026, 10:05 UTC, duration not stated
- Increased latency in Run Query V1 APIs Oct 8, 2026, 00:48 UTC, 1 hour 42 min
- LangSmith Deployment Database Provisioning Error Oct 3, 2026, 05:10 UTC, 5 hours 3 min
Full LangSmith outage history and biggest outages → · Recent outages across all services →
Quotes are the LangSmith Global status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with LangSmith. Times are UTC.