- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 25of 100
What to do
Check whether your product depends on Cerebras. 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 18m it lasted.
Anything that failed between 2025-01-12 14:42 UTC and 2025-01-12 15:00 UTC may need a replay.Subscribe to Cerebras's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cerebras works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cerebras 3
- monitoring
We've deployed the fix and is now recovering. We are actively monitoring service performance.
provider
- investigating
Between 6:15 AM PST and 6:35 AM PST users experienced service disruption with Llama 3.3 70b. We have deployed a fix and the issue is now resolved.
provider
- resolved
Between 6:15 AM PST and 6:35 AM PST users experienced service disruption with Llama 3.3 70b. We have deployed a fix and the issue is now 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-456c249a6a
Is Cerebras still down?
No, this incident was resolved 2025-01-12 15:00 UTC. For Cerebras's live state, see https://down.guide/cerebras.
How long did it last?
18m, from 2025-01-12 14:42 UTC to 2025-01-12 15:00 UTC, by the times Cerebras posted.
What caused it?
Cerebras hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cerebras's official status page, https://status.cerebras.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.