Custom code preprocessors temporarily disabled on Braintrust Cloud
Braintrust has disabled custom code preprocessors on Braintrust Cloud. This may affect conversation display in the Thread view, Topics facets output, and scorers that use a custom preprocessor. Braintrust identified the issue and a fix is in progress. Saved preprocessor code is unchanged and nothing was deleted.
State
Identified
Started
Ongoing for
24 min
Worst impact
Partial outage
Timeline
1 updateIdentified
24 min 100%
Updates
Times in UTCAs posted by Braintrust
We have temporarily disabled custom code preprocessors across Braintrust Cloud while we work on fixing an ongoing issue with it. This may affect how conversations render in the Thread view, and the output of Topics facets and any scorers that rely on a custom preprocessor. Saved preprocessor code is unchanged and nothing has been deleted. Logging, querying, experiments, and all other functionality are unaffected, and no other regions are impacted. A fix is in progress and we expect to re-enable custom code preprocessors shortly.
Braintrust in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
5
Median duration
59 min
This incident
60% shorter than the median
Other Braintrust incidents
All incidentsBraintrust·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