Cerebras

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.

Customer using AWS billing may experience availability issues. Exact reason is being investigated.

This incident has been resolved.

The service is currently inaccessible. We are currently working urgently to restore service capabilities. We will provide further updates as we make progress.

Between 9:07 AM UTC and 9:27 AM UTC users experienced service disruption with qwen-3-235b-a22b-instruct-2507. We have deployed a fix and the issue is now resolved.

Between 9:07 AM UTC and 9:18 AM UTC users experienced partial service disruption with gpt-oss-120b. We have deployed a fix and the issue is now resolved.

Between 10:30 PM PST and 11:42 PM PST 03/17 users experienced partial degradation with glm-4.7. We have deployed a fix and the issue is now resolved.

This incident has been resolved.

The service is currently inaccessible. We are currently working urgently to restore service capabilities. We will provide further updates as we make progress.

We have deployed a fix and the issue is now resolved.

Between 03/16 02:29 PM PST and 03/17 05:00 AM PST users experienced service disruption with glm-4.7. We have deployed a fix and the issue is now resolved.

The service is currently inaccessible. We are currently working urgently to restore service capabilities. We will provide further updates as we make progress.

Between 02:29 PM PT and 02:20 AM PT users experienced service unavailability with GLM-4.7, caused by a datacenter issue.

Between 4:53 UTC ending 5:38 UTC, Qwen 3 235B endpoint experienced a partial service disruption due to a transient network issue. The issue has been identified and fixed, the endpoint is operational.

We identified the issue, applied a fix and are monitoring the endpoint.

Qwen 235B is facing partial service disruption. We are currently working to resume normal service performance. We will provide further updates as we make progress.

This incident has been resolved.

We've identified a fix and our engineering team is deploying this now.

We are currently investigating an issue with zai-glm-4.7 where users are seeing an elevated number of 503 errors. Engineering is working on a resolution.

This incident has been resolved.

Our engineering team has resolved the issue.

We've identified a fix and our engineering team is deploying this now.

We are currently investigating an issue with Llama-3.3-70B where users are seeing an elevated number of 503 errors. Engineering is working on a resolution.

Between 7.30 PM PT and 11 PM PT, the inference service was partially disrupted by 502 Gateway errors across all endpoints. This issue is caused by an internal system dependency, the fix was rolled out and the service is operational across all endpoints.

We are investigating 502 Gateway errors on Cerebras endpoints. We are currently working to resume normal service performance. We will provide further updates as we make progress.

Between 06:00 AM PT and 06:00 PM PT users experienced service disruption with Qwen 3 235B Instruct. We have taken action to address recent changes in traffic patterns and capacity, reducing the disruption. We plan to monitor this endpoint and evaluate restoring rate limits in the next week for Pay Go users.

Between 06:00 AM PT and 06:00 PM PT users experienced service disruption with Qwen 3 235B Instruct. We have taken action to address recent changes in traffic patterns and capacity, reducing the disruption. We plan to monitor this endpoint and evaluate restoring rate limits in the next week for Pay Go users.

As part of recent changes in traffic patterns and capacity, we are temporarily turning down rate limits for Pay-go users to help maintain a positive experience across the board. We understand the challenges this may create for you and your users, and we sincerely apologize for the inconvenience. We plan to monitor this endpoint and evaluate restoring rate limits in the next week. Thank you for your continued partnership and understanding, please reach out to our support team for any other questions.

Qwen 235B performance is degraded and temporarily unavailable for some service tiers. We are currently working to resume normal service performance. We will provide further updates as we make progress.

This incident has been resolved.

Partial of the service has been restored, and we are currently working to resume normal service performance

Qwen 32b is currently inaccessible. We are currently working urgently to restore service capabilities. We will provide further updates as we make progress.

This incident has been resolved.

Between 20:51 and 21:47 UTC users experienced service disruption with GLM 4.7. We have deployed a fix and the issue is now resolved.

A fix has been rolled out, and we are actively monitoring the situation.

Partial of the service has been restored, and we are currently working to resume normal service performance.

The service is currently inaccessible. We are currently working urgently to restore service capabilities. We will provide further updates as we make progress.

Between 12.45 PM PT and 4.00 PM PT users experienced service unavailability with Llama 3.3 70B, caused by a datacenter issue. We have deployed a fix and the issue is now resolved, model endpoint is operational.

Between 12.45 PM PT and 4.00 PM PT users experienced service unavailability with Llama 3.3 70B, caused by a datacenter issue. We have deployed a fix and the issue is now resolved, model endpoint is operational.

The fix has been rolled out and the service has resumed consuming traffic and being monitored.

The issue has been root caused and fix is being implemented to bring the service backup.

The service is currently inaccessible. We are currently working urgently to restore service capabilities. We will provide further updates as we make progress.

Between 4.25 PM PT and 5.45 PM PT, developers experienced minor service disruption due to API Key Error. The issue has been identified and resolved, normal service operation is restored.

This issue is caused by an internal system dependency, and we are currently working to restore system performance.

Partial service disruption due to 401 Error with Unauthorized API Key. We are currently working to resume normal service performance. We will provide further updates as we make progress.

Between 06:50 AM PST and 07:45 AM PST users experienced partial degradation with llama3.1-8b, llama-3.3-70b, qwen-3-32b, qwen-3-235b-instruct-2507 models. We have deployed a fix and the issue is now resolved.

Between 06:50 AM PST and 07:45 AM PST users experienced partial degradation with llama3.1-8b, llama-3.3-70b, qwen-3-32b, qwen-3-235b-instruct-2507 models. We have deployed a fix and the issue is now resolved.

Between 06:50 AM PST and 07:45 AM PST users experienced partial degradation with llama3.1-8b, llama-3.3-70b, qwen-3-32b, qwen-3-235b-instruct-2507 models. We have deployed a fix and the issue is now resolved.

We've deployed the fix and affected service is now recovering. We are actively monitoring service performance.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently working to resume normal service performance. We will provide further updates as we make progress.

Between 01:30 AM PT and 2:30 PM PT users experienced partial degradation with Qwen 3 235B Instruct. We have deployed a fix and the issue is now resolved.

This incident has been resolved.

The platform is accessible now. We are monitoring to ensure stability.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Around 4:09 AM PT, Inference Platform went down causing 500 Internal Server Errors. This issue is caused by a third-party system, and we are currently monitoring.

Between 06:05 AM PST and 09:25 AM PST users experienced partial degradation with Llama-3.3-70B. We have deployed a fix and the issue is now resolved.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

We've deployed the fix and Llama-3.3-70B is now recovering. We are actively monitoring service performance.

From 06:05 AM some features may be temporarily unavailable with Llama-3.3-70B. We are currently working to resume normal service performance. We will provide further updates as we make progress.

We’ve mitigated the issue impacting ZAI-GLM-4.6, and normal performance has been restored.

We are continuing to investigate the issue with ZAI-GLM-4.6. A fix has been deployed, and we are actively monitoring the situation.

Some features may be temporarily unavailable with ZAI-GLM-4.6. We are currently working to resume normal service performance. We will provide further updates as we make progress.

Between 1:30 AM PST and 2:30 AM PST users experienced service disruption with ZAI-GLM-4.6. We have deployed a fix and the issue is now resolved.

This incident has been resolved.

We are continuing to investigate this issue.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

This incident has been resolved.

A fix has been implemented, availability is returning to 100%, and latency times are improving. We will continue to monitor over the next few hours.

Our teams are continuing to work to resolve this issue. We appreciate your patience.

We've identified that the combination of high load and a network routing issue resulted in higher queue times and rejection rates. ETA on resolution is a few hours.

We are experiencing degradation of service across several of our models. Our engineering team is working to identify the root cause and restore stability to our systems.

Between Oct 18th 7 PM PT and Oct 19th 6.30 AM PT users experienced minor service disruption with Llama 3.3 70B, Qwen 3 32B, GPT OSS 120B, Qwen 3 235B Thinking, Qwen 3 Coder 480B because of a datacenter issue. We have deployed the fix and the issue is now resolved.

Update: The issue has been root caused to a city water supply disruption. We are actively working on mitigation.

We are continuing to investigate this issue.

We are experiencing issues with one of our datacenters. We are actively working on mitigation. Seeing minimal degradation of service at this point. Fortunately, this only impacts one datacenter, the rest are operational, and redundancies are in place. ETA recovery time for datacenter: 8 hours. We will actively keep you updated on the progress.

Between 1:35 PM PT and 3:25 PM PT users experienced partial disruption with Qwen 235b Instruct model. We have deployed a fix and the issue is now resolved.

This issue is caused by an internal system dependency, and we are currently working to restore system performance.

We are continuing to investigate this issue.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

A temporary network issue caused partial degradation for the Qwen-3-480B-Coder from 10:36 AM - 11:09 AM PT. The problem has been mitigated and normal performance has been restored.

This incident has been resolved.

Some users are seeing intermittent 404 errors starting around 8 AM PT on 9/12/2025 due to an API gateway routing issue. Engineering is investigating and is working on a prompt resolution.

This incident has been resolved.

Notice: Since approximately 10:40 PM Pacific Time on September 2, 2025, we’ve observed degraded performance due to a datacenter outage. Impact appears limited due to redundancy across other data centers. We will provide further updates as we make progress.

Llama-3.3-70B endpoint experienced reduced availability starting at approximately 7:45am PT. Endpoint went back to full availability starting 8:55am PT.

We observed a temporary increase in latency and intermittent 503 errors for the Llama-3.3-70B model earlier today (between 10:59am Pacific to 11:09am Pacific on 7/31/2025). This was due to ongoing infrastructure operations, including system scaling and maintenance, which briefly reduced available capacity. Service availability and performance are now stabilized.

Llama-3.3-70B, DeepSeek-R1-Distill-Llama-70B, Qwen-3-32B (7/25/2025 from 1:17 PM to 1:41 PM PT) were unavailable. We restored normal service performance at 1:41 PM PT on July 25th.

We had a brief issue this morning (6/25/2025 from 7:25 AM to 9:40 AM PT) affecting the Qwen-3-32B shared endpoint. Some users may have seen 404 or 503 errors during that time.

Some Llama 3.3-70B requests failed due to 5xx errors. We restored normal service performance at 3:54 PM EST on June 19th.

Llama3.1-8B was unavailable. We restored normal service performance at 3:21 PM EST on June 19th.

Some Llama 3.3-70B prompts contained corrupt responses. We restored normal service performance at 1 AM PST on June 9th.

This issue is now resolved.

Service back to normal

The issue has been identified and a fix is being implemented.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

Between 04/30 23:20 UTC and 05/01 01:35 UTC, users experienced partial degradation with Llama-3.3-70B. We have deployed a fix, and the issue is now resolved.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

This issue is caused by an internal system dependency, and we are currently working to restore system performance.

Between 00:28 UTC and 02:58 UTC users experienced partial degradation with Llama3.1-8B. We have deployed a fix and the issue is now resolved.

Between 00:28 UTC and 02:58 UTC users experienced partial degradation with Llama3.1-8B. We have deployed a fix and the issue is now resolved.

We've deployed the fix and Llama3.1-8B is now recovering. We are actively monitoring service performance.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

This incident has been resolved.

We are continuing to investigate this issue.

Between 23:10 UTC and 00:15 UTC users experienced service disruption with DeepSeek-R1-Distill-Llama-70B. We have deployed a fix and the issue is now resolved.

The service is currently inaccessible. We are currently working urgently to restore service capabilities. We will provide further updates as we make progress.

This incident has been resolved.

Resolved

Between March 9th 14:03 UTC and March 10th 16:03 UTC users experienced a minor performance degradation with Llama-3.3-70B and DeepSeek-R1-Distill-Llama-70B. The issue is now resolved.

We've deployed the fix and Llama-3.3-70B and DeepSeek-R1-Distill-Llama-70B are now recovering. We are actively monitoring service performance.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

Between 7:30 PM UTC and 8:00 PM UTC users experienced service disruption with Llama 3.3 70b and Llama 3.1 8b. We have deployed a fix and the issue is now resolved.

We are continuing to investigate this issue.

Some features may be temporarily unavailable. We are currently working to resume normal service performance. We will provide further updates as we make progress.

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.

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.

We've deployed the fix and<affected service> is now recovering. We are actively monitoring service performance.

This incident has been resolved.

We've deployed a fix and the service is now recovering. We are actively monitoring service performance.