Control Plane API Degradation
Braintrust reports degraded performance for queries to the control plane. Braintrust investigated, then monitored the recovery, and now reports the incident as resolved. The incident lasted 45 minutes.
State
Resolved
Started
Lasted
45 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
36 min 79%
Monitoring
9 min 21%
Updates
Times in UTCAs posted by Braintrust
Performance has recovered
Performance has recovered. We are monitoring.
Queries to the control plane are in a degraded state. We are looking into mitigations.
Braintrust in the last 90 days
Full historyIncidents in 90 days
6
Days with an incident
8
Median duration
1 h 1 min
This incident
27% shorter than the median
Other Braintrust incidents
All incidentsBraintrust·Custom code preprocessors temporarily disabled on Braintrust Cloud
Custom code preprocessors did not work on Braintrust Cloud. This affected the Thread view, Topics facets, and scorers that use a custom preprocessor. Braintrust identified the issue, deployed a fix, and re-enabled the preprocessors. The issue is resolved and lasted about 3 days.
Braintrust·Elevated errors and latency on the US data plane API
The issue has been resolved.
Braintrust·Slow or failed data loading in US region
The issue causing slow or failed data loading in our US-hosted service has been resolved. We're sorry for the disruption.
Braintrust·Elevated 5XXs on Control Plane API
The issue causing elevated errors in the Braintrust control plane APIs has been resolved.
Braintrust·Upstream package mirror is degraded, Brainstore is not currently affected
The upstream APT package mirror in AWS us-east-1 has recovered and we're no longer seeing impact when starting new brainstore instances.
Follow Braintrust
Your coding agent knows when Braintrust is down, and tells you when a failure is theirs, not yours. You can also get Braintrust incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "braintrust" and tell me if Braintrust has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=braintrust/feed subscribe https://outages.live/feed.xml?providers=braintrustFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane