Partial Service Disruption
OutageThe incident has been resolved
Cerebras is up and running. Cerebras serves low-latency inference for AI models.
Worked out from the incidents Cerebras reported, so it is an estimate and not a measurement.
Last incident: “Partial Service Disruption”, 28 days ago.
The incident has been resolved
Between 11:00 and 11:15 UTC users experienced partial degradation with Gemma-4-31B. Service has been restored.
GPT-OSS-120B was having partial service disruption between 18:20 UTC to 18:45 UTC. This is resolved now.
AWS billing issue is fixed now.
This incident has been resolved.
Cerebras’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Cerebras reported was “Partial Service Disruption”, 28 days ago (2026-09-25 12:16 UTC). Its last full outage started 28 days ago.
Cerebras reports 3 components on its status page, including GPT-OSS-120B, Developer Console, Qwen-3.8-27b. Each is checked again whenever this page refreshes.
Retry with exponential backoff, fall back to another model or provider if your product allows it, and avoid hammering the API while it recovers.
No — the status page tracks individual models (for example the hosted open-weight models) plus the Developer Console as separate rows.
Match the failing endpoint to its model row — Cerebras' page is per-model, so a single-deployment event leaves the rest of the API untouched.
If the status above is operational but Cerebras still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.