- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Braintrust. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-06-04 01:23 UTC and 2026-05-16 18:50 UTC may need a replay.Subscribe to Braintrust's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=braintrust works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Braintrust 2
- investigating
On May 15, some automations stopped running which impacted scorer executions.
provider
- resolved
We determined the issue was caused by a role used by the automation service losing required permissions following a configuration change. The issue was reported on May 15 at approximately 1:00 PM PT and resolved on May 16 at 11:50 AM PT. To help prevent similar incidents, we have improved our alerting and added audit logging for role and permission changes.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-3722e37892
Is Braintrust still down?
No, this incident was resolved 2026-05-16 18:50 UTC. For Braintrust's live state, see https://down.guide/braintrust.
How long did it last?
0m, from 2026-06-04 01:23 UTC to 2026-05-16 18:50 UTC, by the times Braintrust posted.
What caused it?
Braintrust hasn't published a root cause. If it does, it shows here.
Where does this come from?
Braintrust's official status page, https://status.braintrust.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.