- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 43of 100
What to do
Check whether your product depends on LangSmith. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 42m it lasted.
Anything that failed between 2026-10-08 00:48 UTC and 2026-10-08 02:30 UTC may need a replay.Subscribe to LangSmith's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=langsmith works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from LangSmith 3
- investigating
We are investigating a latency increase in our V1 Run Query APIs. V2 Run Query APIs backed by SmithDB are unaffected.
provider
- monitoring
Query API performance is back to normal after capacity adjustment. We are currently monitoring for further problems.
provider
- resolved
Capacity remained stable in the last hour. Incident resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d340449c7f
Is LangSmith still down?
No, this incident was resolved 2026-10-08 02:30 UTC. For LangSmith's live state, see https://down.guide/providers/langsmith.
How long did it last?
1h 42m, from 2026-10-08 00:48 UTC to 2026-10-08 02:30 UTC, by the times LangSmith posted.
What caused it?
LangSmith hasn't published a root cause. If it does, it shows here.
Where does this come from?
LangSmith's official status page, https://global.status.smith.langchain.com/gcp-us, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.