- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 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 48m it lasted.
Anything that failed between 2026-05-05 23:35 UTC and 2026-05-06 00:23 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 5
- investigating
We're observing a high rate of errors on the production control plane which is causing errors on braintrust.dev and data plane operations.
provider
- identified
We have identified the cause and are working with an upstream provider on a fix.
provider
- monitoring
We are actively monitoring the fix.
provider
- resolved
We are no longer seeing issues.
provider
- resolved
The issue was caused by our firewall provider unexpectedly blocking traffic despite safeguards we had in place to prevent this behavior. We are actively working with the vendor on additional mitigation measures to reduce the likelihood of this occurring again.
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-107c96835c
Is Braintrust still down?
No, this incident was resolved 2026-05-06 00:23 UTC. For Braintrust's live state, see https://down.guide/braintrust.
How long did it last?
48m, from 2026-05-05 23:35 UTC to 2026-05-06 00:23 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.