- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dedicated Inference
- Regions
- us, us-east1
What to do
Check whether you use Baseten Dedicated Inference in us, us-east1. 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 2h it lasted.
Anything that failed between 2026-05-15 01:00 UTC and 2026-05-15 03:00 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.
Updates from Baseten 2
- investigating
Elevated errors in our us-east1 cluster
provider
- resolved
This incident has been resolved.
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-497bc655a1
Is Baseten still down?
No, this incident was resolved 2026-05-15 03:00 UTC. For Baseten's live state, see https://down.guide/baseten.
How long did it last?
2h, from 2026-05-15 01:00 UTC to 2026-05-15 03:00 UTC, by the times Baseten posted.
What was affected?
Baseten named Dedicated Inference in us, us-east1.
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.