# LLM Gateway service interruption

- Provider: [LangSmith](https://down.guide/providers/langsmith)
- Confidence: Confirmed
- Impact: Major outage
- lasted 0m
- started 2026-10-08 10:05 UTC
- LangSmith states the impact was 2026-10-08 07:08 to 07:43 UTC (35m)
- id: DWN-fcd9fdea78
- Official page: https://global.status.smith.langchain.com/incidents/01M4DFKCK22TD3N84814NSJJ9W

## Root cause
> It was due to an incorrect infrastructure configuration change that stopped traffic from reaching the gateway.

Category: Deploy or config change. [Postmortem](https://global.status.smith.langchain.com/incidents/01M4DFKCK22TD3N84814NSJJ9W)

## Updates from LangSmith
### 2026-10-08 07:08 UTC: investigating
The LLM Gateway (gateway.smith.langchain.com (http://gateway.smith.langchain.com)) is returning an elevated rate of 502 errors. We are investigating.

### 2026-10-08 07:43 UTC: resolved
From 07:08 to 07:43 UTC on October 8, 2026, the LLM Gateway (gateway.smith.langchain.com (http://gateway.smith.langchain.com)) returned high 502 error rates. It was due to an incorrect infrastructure configuration change that stopped traffic from reaching the gateway.
We fully restored the service at 07:43 UTC, and no other LangSmith services were affected. We're sorry for the disruption.

From the builder: does your app depend on LangSmith? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=langsmith) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention LangSmith.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-fcd9fdea78), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.