← Back to the carnage
LANGSMITH

🟡 LangSmith's bulk exports are throwing errors like confetti at a failed startup pitch. Turns out exporting data in bulk is harder than exporting yourself from a bad relationship. Currently investigating why their 'bulk' feature forgot how to move things. (Auto-resolved: no updates in 24h)

⏰ Sep 01, 2026 Fixed (for now) spotted via status_rss

// The official story

Elevated error rate for bulk exports

// Status page says

Status: Investigating We are investigating an elevated error rate for bulk exports executions. Bulk exports are currently delayed. Affected components LangSmith Bulk Exports (Partial outage)

🔗 Official status page (for the PR-approved version)

https://global.status.smith.langchain.com/gcp-us/incidents/01M1F7YFCY82QF6FAX9CMRSTTM

Langsmith's Greatest Hits

🟢 LANGSMITH 1d ago
🟡 LangSmith's authentication layer is playing hard to get—some login attempts timeout while others fail outright. Already-logged-in users watching the chaos unfold safely from inside. Engineers are 'investigating' which tech speak for 'we're checking the logs for the first time today.'. (Auto-resolved: no updates in 24h)
🟢 LANGSMITH Oct 03, 2026
🟡 LangSmith deployments are choking during database setup across GCP regions—turns out their cloud provider's infrastructure decided to take an unscheduled nap. The Control Plane is having an identity crisis and can't spin up new dedicated instances. Someone's definitely stress-testing their oncall rotation right now. (Auto-resolved: no updates in 24h)
🟢 LANGSMITH Sep 02, 2026
🟡 LangSmith's agent sandbox is ghosting newly created agents on shared hardware. The good news: existing agents still work. The bad news: they're watching the new kids suffer. Engineers are investigating why initialization decided to take a personal day. (Auto-resolved: no updates in 24h)
🟢 LANGSMITH Aug 20, 2026
🟡 LangSmith's build pipeline decided new revisions aren't worth processing. Control plane is having an existential crisis in GCP US. Engineers are investigating why their deployment factory forgot how to manufacture deployments. (Auto-resolved: no updates in 24h)