Anthropic’s status page listed elevated Claude API error rates as under investigation early Friday. Several Claude services were marked as degraded after earlier resolved incidents on June 19 and June 18.

Claude is not listed as fully down, but Anthropic is investigating elevated error rates affecting several Claude services. Users seeing errors or failed requests should check Anthropic Status before assuming the problem is local.
At the latest check, Anthropic’s status page showed degraded performance for the Claude web app, Claude Console, Claude API, Claude Code and Claude Cowork. Claude for Government remained listed as operational.
The active incident was posted at 4:17 a.m. ET and was still marked “Investigating” when checked. Anthropic described the issue as elevated error rates on the Claude API.
That means some users may be able to access Claude while others see errors, slow responses or failed requests. The status page did not describe the issue as a complete shutdown.
Anthropic’s active incident page listed these services as affected:
The company has not posted a cause or a fix timeline for the current elevated-error incident. For developers, the Claude API listing is the most important part of the update because it can affect apps, tools and automations that depend on Claude responses.
Earlier Friday, Anthropic marked a separate incident, “Elevated errors for Claude Opus 4.8,” as resolved. That issue moved from investigating at 2:07 a.m. ET to monitoring at 3:03 a.m. ET and resolved at 3:17 a.m. ET. Anthropic said that incident affected the Claude web app, Console, API, Claude Code and Claude Cowork.
On Thursday, Anthropic also reported a service disruption on the Claude web app. The company said impact lasted from 2:55 a.m. to 3:40 a.m. ET, and the incident was later marked resolved.
Those resolved incidents explain why users may see recent outage references even though the current issue is a newer elevated-error investigation.
If Claude is returning errors while Anthropic lists degraded performance, the first step is to check the official status page and wait for the next update.
Users can also try a fresh browser session, a different device, a different network or the Claude mobile app to rule out a local browser or connection problem. API users should monitor their own logs and avoid aggressive repeated retries while Anthropic is investigating.
If Anthropic marks the incident resolved and Claude still fails, the problem may be local to an account, browser, network, extension or integration.
Anthropic has not said how many users are affected, whether the current issue is limited to certain regions, or whether it is related to the earlier June 19 Opus 4.8 incident or the June 18 Claude web app disruption.
This page will be updated when Anthropic posts a new investigating, monitoring or resolved update.


