Live  /  Braintrust  /  Incident

Braintrust: Custom code preprocessors temporarily disabled on Braintrust Cloud

Braintrust · braintrust.devMinor incidentmonitoring2026-11-14 15:29 UTC
Public — what happened

Summary

Braintrust said it turned off custom code preprocessors across its Cloud service starting 2026-11-13 at 01:21 UTC while it worked on an ongoing problem it had identified. The company said this could change how conversations appear in the Thread view and affect Topics facet results and any scorers that depend on a custom preprocessor, while saved code was kept and logging, querying and experiments were not affected. On 2026-11-14 at 15:29 UTC, Braintrust said it had deployed a fix and turned the feature back on, and it is now monitoring for any recurrence.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Braintrust against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Braintrust: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Braintrust report →

More from Braintrust

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Braintrust status & history page.

Related: Braintrust status & history. SquidGrid is not affiliated with Braintrust.