Is LangSmith down? › Outage history › Sep 2, 2026

LangSmith partial outage on Sep 2, 2026: what happened

On Sep 2, 2026, the LangSmith Global status page reported "Agent-scoped sandbox fails to initialize on new agents". About 3 hours 43 min: from Sep 2, 2026, 17:04 UTC to Sep 2, 2026, 20:47 UTC, by the official start and resolution times.

LangSmith right now

At our last refresh (Oct 22, 2026, 12:35 UTC) LangSmith was having problems: Partial System Degradation.

Is LangSmith down right now? →
Started
Sep 2, 2026, 17:04 UTC
Resolved
Sep 2, 2026, 20:47 UTC
Duration
3 hours 43 min
Official impact
Major
Source
Agent-scoped sandbox fails to initialize on new agents on the LangSmith Global status page

The LangSmith Global status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.

What caused the LangSmith partial outage?

The LangSmith Global status page has not published a cause. When it identified the problem at 17:59 UTC on Sep 2, 2026, it said: "We have identified the root cause of this incident and are actively working on a fix. The issue originates from a recent change to how sandbox slugs are generated in our backend systems, which now derive slugs directly rather than referencing sandbox IDs. This has introduced a mismatch between the values returned by the backend and those the frontend expects. We will share a further update as remediation progresses."

When was it fixed?

The LangSmith Global status page marked it resolved at Sep 2, 2026, 20:47 UTC, 3 hours 43 min after it started. A fix was in place and being monitored from Sep 2, 2026, 20:32 UTC. Its resolution note: "All systems are operational"

Timeline of official updates

Every update the LangSmith Global status page posted, oldest first. Times are UTC.

  1. Sep 2, 2026, 17:04 UTC investigating

    This affects only newly created agents with a shared computer.

  2. Sep 2, 2026, 17:59 UTC identified

    We have identified the root cause of this incident and are actively working on a fix. The issue originates from a recent change to how sandbox slugs are generated in our backend systems, which now derive slugs directly rather than referencing sandbox IDs. This has introduced a mismatch between the values returned by the backend and those the frontend expects. We will share a further update as remediation progresses.

  3. Sep 2, 2026, 20:32 UTC monitoring

    The fix has been deployed. All systems are operational

  4. Sep 2, 2026, 20:47 UTC resolved

    All systems are operational

LangSmith partial outage questions

What caused the LangSmith partial outage on Sep 2, 2026?

The LangSmith Global status page has not published a cause. When it identified the problem (Sep 2, 2026, 17:59 UTC) it said: "We have identified the root cause of this incident and are actively working on a fix. The issue originates from a recent change to how sandbox slugs are generated in our backend systems, which now derive slugs directly rather than referencing sandbox IDs. This has introduced a mismatch between the ..."

When was the LangSmith partial outage on Sep 2, 2026 fixed?

The LangSmith Global status page marked it resolved at Sep 2, 2026, 20:47 UTC, 3 hours 43 min after it started. A fix was in place and being monitored from Sep 2, 2026, 20:32 UTC. Its resolution note: "All systems are operational"

How long did the LangSmith partial outage last?

About 3 hours 43 min: from Sep 2, 2026, 17:04 UTC to Sep 2, 2026, 20:47 UTC, by the official start and resolution times.

Was LangSmith completely down?

No. The LangSmith Global status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.

Other recent LangSmith incidents

Full LangSmith outage history and biggest outages → · Recent outages across all services →

Quotes are the LangSmith Global status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with LangSmith. Times are UTC.