dev.to24 de junio de 2026NUEVO AFECTA AL EXAMEN
ModeloAPI

Claude Opus 4.8 is seeing elevated errors across API, Claude Code, and Console

Anthropic is investigating elevated Claude Opus 4.8 errors, with Claude API, Claude Code, Console, claude.ai, and Claude Cowork marked degraded.

# Claude Opus 4.8 is seeing elevated errors across API, Claude Code, and Console

Anthropic is investigating elevated error rates on Claude Opus 4.8, and the status page currently marks Claude API, Claude Code, Claude Console, claude.ai, and Claude Cowork as degraded. If your product or internal workflow depends on Opus 4.8, this is a real-time reliability issue rather than normal model chatter.

What Anthropic has confirmed

Anthropic opened the incident at 13:16 UTC on 24 June 2026 under the title “Elevated error rate on Claude Opus 4.8.” The incident is still listed as **investigating** at the time of writing.

Affected components were moved from operational to degraded performance:

  • claude.ai
  • Claude Console at platform.claude.com
  • Claude API at api.anthropic.com
  • Claude Code
  • Claude Cowork

The incident impact is marked as minor on Anthropic’s status API, but the affected surface area matters: this is not just the consumer chat app. It includes the API and Claude Code, which means builder-facing automation, agent runs, coding workflows, and production fallbacks can all be touched if they route through Opus 4.8.

What builders should do now

If you are using Claude Opus 4.8 in production, check your error budgets and retry behavior now. The practical move is to route latency-sensitive or customer-facing traffic to a fallback model until Anthropic moves the incident to monitoring or resolved.

For engineering teams using Claude Code, avoid kicking off long unattended work if the task cannot tolerate failed tool calls or partial agent progress. If you are in the middle of a deployment, keep human review tight and capture logs for failed runs so you can separate your own code issues from upstream model errors.

For founders and product teams, this is also a reminder to avoid single-model dependency for critical workflows. A fallback path to another Claude tier, OpenAI, Gemini, or a local/open model will not produce identical output, but it can keep the user experience alive during incidents like this.

Caveats

Anthropic has not yet published a root cause, ETA, or detailed error profile. The status page names Opus 4.8 specifically, so do not assume every Claude model is equally affected unless your own telemetry shows it.

We will treat this as resolved only when Anthropic updates the incident or the affected components return to operational.

Sources

  • Anthropic incident API: https://status.claude.com/api/v2/incidents/8b0rggdfh1hv.json
  • Anthropic status summary: https://status.claude.com/api/v2/summary.json
  • Public incident page: https://stspg.io/wnw8wdn9sfwm
Leer artículo completo en dev.to