Live  /  xAI  /  Incident

xAI: [Third-party models] Opus 5.5 is Experiencing 429s

xAI · x.aiResolved2026-10-08 13:54 UTC
Public — what happened

Summary

xAI said that a third-party model, Opus 5.5, was having problems that showed up as 429 errors, and it classed the incident as a disruption. The company said it began investigating at 13:54 UTC on 8 October 2026 and described the degradation as affecting Opus 5.5 wherever it is used across its product components. At 14:08 UTC xAI reported that a fix had been put in place and that it was watching for service to recover, and it marked the incident resolved at 15:31 UTC. No cause was given in the text.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach xAI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for xAI: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the xAI report →

More from xAI

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the xAI status & history page.

Related: xAI status & history. SquidGrid is not affiliated with xAI.