outages.live
Live
BraintrustIncident · 2026-08-19 18:01 UTC

Upstream package mirror is degraded, Brainstore is not currently affected

ResolvedOfficial update

The upstream APT package mirror in AWS us-east-1 has recovered and we're no longer seeing impact when starting new brainstore instances.

The latest update from Braintrust.

State

Resolved

Started

74 d ago

2026-08-19 18:01 UTC

Lasted

4 h 33 min

until 2026-08-19 22:35 UTC

Worst impact

Notice

Timeline

2 updates
18:0119:1020:1821:2722:35
NoticeUpdate postedTimes in UTC

Monitoring

4 h 33 min 100%

Updates

Times in UTC

As posted by Braintrust

Resolved2026-08-19 22:35 UTC

The upstream APT package mirror in AWS us-east-1 has recovered and we're no longer seeing impact when starting new brainstore instances.

Monitoring2026-08-19 18:01 UTC

The upstream APT package mirror on AWS us-east-1 is degraded. **There is currently no downtime** and we are looking into alternative package mirrors in the meantime. Please note that for **both the Braintrust-hosted data plane and self-hosted data planes:** EC2 instance replacement due to healthcheck failures or deploys may result in failed instance initialization and downtime until the upstream issue is resolved.

Braintrust in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

59 min

This incident

4.6× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 33 min
median 59 min
90 days agoToday

Other Braintrust incidents

All incidents

Braintrust·Elevated errors and latency on the US data plane API

The issue has been resolved.

Resolvedresolved 33 d ago

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.

Resolvedresolved 53 d ago

Braintrust·Elevated 5XXs on Control Plane API

The issue causing elevated errors in the Braintrust control plane APIs has been resolved.

Resolvedresolved 58 d ago

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=braintrust
Slack
/feed subscribe https://outages.live/feed.xml?providers=braintrust

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane