LangSmith outage history
We record LangSmith's status every five minutes and have not recorded an incident from LangChain's status page yet. We never invent one.
Uptime & history
Tracking since Jun 22, 2026% of our checks that found LangSmith fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.
How LangSmith fails
Since Jun 28, 2026, LangChain's status page has marked 2 LangSmith components as impaired, across 10 of our five-minute readings. LangSmith Deployments Control Plane accounts for the most: 9 readings (45 minutes) on 1 day, most recently on Jul 16, 2026. Next is LangSmith Run Ingestion, with 1 readings on 1 day.
| Component | Outage | Degraded | Maint. | Days | Last |
|---|---|---|---|---|---|
| LangSmith Deployments Control Plane | — | 9 | 1 | 1 | Jul 16, 2026 |
| LangSmith Run Ingestion | — | 1 | — | 1 | Jul 12, 2026 |
| LangSmith API | — | — | 1 | 1 | Jun 28, 2026 |
| LangSmith Application | — | — | 1 | 1 | Jun 28, 2026 |
| LangSmith Billing | — | — | 1 | 1 | Jun 28, 2026 |
| LangSmith PromptHub | — | — | 1 | 1 | Jun 28, 2026 |
Counts are five-minute readings of LangChain's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.
Incidents and their updates are LangChain's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with LangChain.