Baseten: Elevated errors for dedicated inference in a subset of clusters

What to do

Check whether you use Baseten Dedicated Inference. 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 14m it lasted.
Anything that failed between 2026-06-26 22:00 UTC and 2026-06-26 22:15 UTC may need a replay.
Subscribe to Baseten's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=baseten works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingJun 26, 2026, 10:00 PM UTC
We are currently investigating this issue.
provider
identifiedJun 26, 2026, 10:01 PM UTC
The issue has been identified and a fix is being implemented.
provider
identifiedJun 26, 2026, 10:03 PM UTC
Nearly all clusters have recovered.
provider
identifiedJun 26, 2026, 10:11 PM UTC
We are continuing to work on a fix for this issue.
provider
resolvedJun 26, 2026, 10:15 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Baseten still down?

No, this incident was resolved 2026-06-26 22:15 UTC. For Baseten's live state, see https://down.guide/baseten.

How long did it last?

14m, from 2026-06-26 22:00 UTC to 2026-06-26 22:15 UTC, by the times Baseten posted.

What was affected?

Baseten named Dedicated Inference.

What caused it?

Baseten hasn't published a root cause. If it does, it shows here.

Where does this come from?

Baseten's official status page, https://status.baseten.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.