Cerebras stock pops 9% after Sam Altman calls the chipmaker a 'close partner'
- ID
- 31829
- Status
- summarized
- Published
- 05 Oct 2026, 9:37 PM
- Fetched
- 05 Oct 2026, 10:52 PM
- Provider
- CNBC Technology
- Category
- technology
- Original URL
- https://www.cnbc.com/2026/10/05/cerebras-cbrs-sam-altman-close-partner.html
- Source URL
- https://www.cnbc.com/id/19854910/device/rss/rss.html
Summary
- Score
- 3.5
- Created
- 05 Oct 2026, 10:53 PM
- Tags
- Audience
- developersai_ml_learnerssaas_startup_founders
What happened
Cerebras (CBRX) shares rose about 6% in premarket Monday to roughly $177 after OpenAI CEO Sam Altman posted on X that Cerebras is a "close partner" with a "deep engagement pushing on the frontiers of speed." The bounce followed a 20% single-week drop after it was revealed OpenAI would power the "Ultrafast" mode for GPT-6.1 Sol with Nvidia GPUs instead of Cerebras chips. Cerebras IPO'd on Nasdaq in May 2026 and the stock is now down nearly half from its highs, with the piece attributing the swing largely to Altman's Friday post.
Why it matters
The concrete fact for builders is that OpenAI's fastest-serving mode for GPT-6.1 Sol is now Nvidia-backed, not Cerebras-backed, so latency assumptions tied to that mode should be re-checked against current provider docs rather than earlier benchmarks. It is also a reminder that a single frontier-model hardware decision can move an inference vendor's valuation 20% in a week — if you are choosing an inference provider for a latency-sensitive product, get capacity and roadmap commitments in writing rather than reading them off a CEO tweet. The article offers no Malaysia-specific detail, so no local policy, pricing, or infra takeaway can be drawn from it.
Discussion angle
Should builders treat inference-vendor choice as a technical benchmark decision or a supplier-risk decision? Use this case — GPT-6.1 Sol's Ultrafast mode moving to Nvidia GPUs while Altman still calls Cerebras a 'close partner' — to talk through what questions to ask an inference vendor before you commit a latency-sensitive workload.