30 days uptime
100.000%
30 of 30 days clean · 0m total downtime
All windows
Last resolved incident
4 days ago · lasted 10m · None
5/22/2026, 5:20:10 PM · resolved 5/22/2026, 5:30:19 PM · Resolved
5/14/2026, 4:55:22 PM · resolved 5/16/2026, 12:40:19 AM · Resolved
5/13/2026, 1:00:53 PM · resolved 5/13/2026, 2:00:51 PM · Resolved
Official status page: https://status.smith.langchain.com (opens in new tab)
Live status pill for LangSmith. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=langsmith"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/langsmith" style="border:0;width:260px;height:44px" loading="lazy" title="LangSmith status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/langsmith)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/langsmith/badge.svgLangSmith 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 4 days ago and lasted 10 minutes (an incident).
Looking for the live "is LangSmith down" view? See the LangSmith Status page.
LangSmith's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
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.