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
Currently up for 87d 2h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
100%
0 incidents · no downtime
2015 checks
Operational · 30d
100%
0 incidents · no downtime
8638 checks
Operational · since Jun 22, 2026
100%
0 incidents · ≈55m degraded
41625 checks

% 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.

Recent checks
oldernow

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.

ComponentOutageDegradedMaint.DaysLast
LangSmith Deployments Control Plane—911Jul 16, 2026
LangSmith Run Ingestion—1—1Jul 12, 2026
LangSmith API——11Jun 28, 2026
LangSmith Application——11Jun 28, 2026
LangSmith Billing——11Jun 28, 2026
LangSmith PromptHub——11Jun 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.