From approximately 1550 until 1610 UTC, the LangSmith API, UI, and Run Ingest were intermittently unavailable due to an API error from our metering provider that caused a 500 response on the /orgs/current endpoint and a 403 response on some calls to other LangSmith API endpoints including /runs and /runs/batch.
These errors are no longer occurring and we are working to reduce our dependency on our metering provider for the majority of these calls in the future.
Resolved
From approximately 1550 until 1610 UTC, the LangSmith API, UI, and Run Ingest were intermittently unavailable due to an API error from our metering provider that caused a 500 response on the /orgs/current endpoint and a 403 response on some calls to other LangSmith API endpoints including /runs and /runs/batch.
These errors are no longer occurring and we are working to reduce our dependency on our metering provider for the majority of these calls in the future.
Monitoring
From approximately 1550 until 1610 UTC, the LangSmith API, UI, and Run Ingest were intermittently unavailable due to an API error from our metering provider. The error has ceased and we are monitoring for any recurrence.
Investigating
We are investigating an issue that is causing the portions of the LangSmith UI to fail to load with a console error 500 for the /orgs/current endpoint.
Looking for the EU status page? Find it here: https://eu.status.smith.langchain.com
