Between 2332 and 0017 UTC on July 11-12 an issue with our database provider resulted in a failure to run queries against the database that hosts LangSmith runs and feedback.
This caused failures of all run query calls to the LangSmith API, prevented the loading of runs in the LangSmith UI and prevented the submission of feedback.
We are continuing to monitor for a recurrence and are working with our database provider to understand the root cause and will take steps to mitigate future impact once we learn more.
Posted Jul 12, 2024 - 00:38 UTC
Update
Since 2332UTC, we continue to experience an issue with our database provider that is resulting in 500 errors when calling the LangSmith API, including submitting feedback, and is also impacting the LangSmith Frontend. Runs are still being ingested but experiencing significant delays before appearing in the LangSmith UI. We are actively engaged with our database provider and are continuing to investigate.
Posted Jul 11, 2024 - 23:58 UTC
Investigating
Since 2332UTC, an issue with our database provider is resulting in 500 errors when calling the LangSmith API, including submitting feedback, and is also impacting the LangSmith Frontend. Runs are still being ingested but may experience longer than normal delays before appearing in the LangSmith UI. We are in touch with our database provider and are actively investigating.
Posted Jul 11, 2024 - 23:43 UTC
This incident affected: LangSmith Run Ingestion, LangSmith Frontend, and LangSmith API.