CheckUpstream measured LangSmith at 100.000% availability across 2032 independent checks (global · api). 16 incidents were recorded in the past 12 months; the most recent resolved 5 days ago after 38 minutes. Status signals are polled from LangSmith's official incident.io status page, alongside independent probes and community reports.
90 days measured availability how this is computed
100.000%
global · api · n=2032 · p95 380ms (30d)
Share of our own checks against LangSmith endpoints that returned LangSmith's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 6 incidents · 84 of 90 days with none posted · 5h 46m of declared impact
Fewer incidents in the last 30 days than 17% of 232 tracked services.
Share of each window with no impact declared by LangSmith
7d
99.736%
30d
99.197%
90d
99.732%
180d
99.866%
1y
99.934%
Downtime like this can be refundable
If you're a paying LangSmith customer, outages in these windows may count against LangSmith's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your LangSmith entitlement →Does LangSmith actually matter to you?
A LangSmith outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 6 incidents LangSmith published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long LangSmith takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 26, 16:27 UTC · resolved in 38m · Resolved
Aug 20, 15:54 UTC · resolved in 2h 45m · Resolved
Aug 19, 15:39 UTC · resolved in 1h · Resolved
Aug 6, 15:33 UTC · resolved in 37m · Resolved
Live LangSmith status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/langsmith)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
LangSmith is currently Operational. CheckUpstream tracks LangSmith in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
LangSmith's last resolved incident started 5 days ago and lasted 38 minutes (a partial outage).
Looking for the live "is LangSmith down" view? See the LangSmith Live status page.
Aug 5, 15:27 UTC · resolved in 6h 34m · Resolved
Aug 3, 18:20 UTC · resolved in 59m · Resolved
LangSmith's 30-day measured availability is 100.000%, from CheckUpstream's own probes against LangSmith endpoints. It is the share of checks that returned the expected response, not a figure taken from LangSmith's status page.
Sign up to CheckUpstream and add LangSmith to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll LangSmith's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.