TL;DR
Anthropic restored Claude after a major outage disrupted authentication and performance across several services on August 16, 2026. Claude.ai, Claude Code and Claude Cowork were affected, while the Claude API remained operational; Anthropic has not disclosed the cause.
Anthropic restored Claude after a major outage on August 16 disrupted authentication and performance across Claude.ai, Claude Code and Claude Cowork, interrupting access to tools used for chat, software development and workplace tasks. The company said all services had recovered by 22:40 UTC.
The incident began at about 21:58 UTC, when Anthropic said it was investigating an issue preventing some users from authenticating to Claude.ai, Claude Code and Claude Cowork. Affected users could encounter login failures, pages that would not load, incomplete requests or other service errors.
At 22:07 UTC, Anthropic reported a broader disruption involving degraded performance on Claude.ai and platform.claude.com. Its status page classified Claude.ai, Claude Code and Claude Cowork as experiencing a major outage while the investigation continued.
The Claude Console and Claude API were listed as operational during the disruption, according to the reported status information. Anthropic announced at 22:40 UTC that all services had been restored, placing the interruption at roughly 42 minutes from the first reported authentication problem to recovery.
Claude restored after a major outage
Authentication failures and degraded performance disrupted Claude.ai, Claude Code, and Claude Cowork. Anthropic reported full restoration at 22:40 UTC; the Claude API remained operational.
How the outage unfolded
The event began as an authentication problem and was later described as broader performance degradation before Anthropic announced recovery.
Authentication failures
Anthropic began investigating an issue preventing some users from signing in to Claude.ai, Claude Code, and Claude Cowork.
Impact broadens
Degraded performance was reported on Claude.ai and platform.claude.com while the investigation continued.
Services restored
Anthropic announced that all services had recovered, ending the confirmed incident window after roughly 42 minutes.
Authentication issue → broader service degradation → full restoration
What was affected
The disruption centered on user-facing products and access pathways. Direct API availability limited the impact for applications communicating with Claude models programmatically.
Claude.ai
Users could face failed logins, pages that did not load, incomplete requests, or other service errors.
Claude Code
Authentication and access problems could interrupt active software-development sessions and coding workflows.
Claude Cowork
Workplace tasks built around Anthropic’s connected collaboration tools could be delayed or blocked.
Claude Platform
Anthropic specifically reported degraded performance on platform.claude.com during the incident.
Claude API
The API remained available according to the reported status information, reducing downstream application impact.
Claude Console
The Console was listed as operational while the major outage affected other Claude services.
| Service | Reported state | Primary risk | Recovery |
|---|---|---|---|
| Claude.ai | ✗ Major outage | Login and request failures | ✓ Restored |
| Claude Code | ✗ Major outage | Interrupted coding sessions | ✓ Restored |
| Claude Cowork | ✗ Major outage | Delayed workplace tasks | ✓ Restored |
| platform.claude.com | ~ Degraded | Reduced platform performance | ✓ Restored |
| Claude API | ✓ Operational | Limited confirmed impact | ✓ Operational |
Status reflects Anthropic’s reported incident information.
One access problem, multiple interrupted workflows
Claude is delivered through connected products rather than a single chat page. A shared authentication or platform-layer failure can therefore block several kinds of work at once.
Confirmed facts versus open questions
Anthropic confirmed the service impact and restoration, but it did not publish a root cause, affected-user count, regional breakdown, or evidence that requests were lost.
Relative certainty of key claims
The primary recovery milestone was publicly reported by Anthropic.
Available information does not support attributing the outage to malicious activity.
No public details establish whether capacity, software, infrastructure, or another internal issue caused the outage.
A post-incident report could explain the cause, affected systems, and corrective work.
The practical answers
The confirmed record is limited to Anthropic’s status updates and recovery notice.
Is Claude still down?
No. Anthropic said all services were restored by 22:40 UTC on August 16, 2026. Isolated errors may require a fresh login or local troubleshooting.
How long did it last?
Approximately 42 minutes elapsed between the first authentication alert at 21:58 UTC and the restoration notice.
Was the API affected?
No confirmed API outage. Anthropic listed the Claude API as operational during the disruption.
What caused the outage?
The cause remains undisclosed. Capacity, infrastructure, software changes, and authentication systems are unconfirmed possibilities—not established facts.
Still seeing an error?
Check Anthropic’s current status page, retry authentication, and determine whether your workflow uses an affected interface or the operational API.
Claude Workflows Faced Disruption
The outage mattered because Claude is used through several connected products rather than only a consumer chat page. Problems reaching Claude Code could interrupt coding sessions, while failures in Claude Cowork could delay tasks built around Anthropic’s workplace tools. Login failures can also block users before they reach otherwise functioning services.
The reported availability of the Claude API limited the impact for developers whose applications communicate directly with Anthropic’s models. Even so, the disruption showed how an authentication or platform-level problem can affect multiple user-facing products at once, including services that businesses may rely on during active work.
AI development tools for programmers
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
How the Outage Unfolded
Anthropic’s first update focused on authentication failures across three products. The company then expanded its description to include degraded performance on Claude.ai and its platform site, indicating that the incident was not confined to a single login screen or product interface.
The service classifications also changed as Anthropic investigated. During the incident, Claude.ai, Claude Code and Claude Cowork carried a major-outage designation, while the API remained operational. The recovery notice followed less than an hour after the first acknowledgment, without a public explanation of the underlying technical failure.
“We are investigating an issue preventing some users from authenticating to Claude.ai, Claude Code, and Claude Cowork.”
— Anthropic status update at 21:58 UTC
AI-powered coding assistant software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Outage Cause Still Undisclosed
Anthropic has not disclosed the cause of the outage or explained whether the authentication failures and degraded performance originated from the same technical problem. No public details establish whether the disruption involved capacity, a software change, infrastructure failure or another internal issue.
It is also unclear how many users were affected, whether the impact varied by region or account type, and whether any requests were lost rather than delayed. There is no confirmed indication of a security incident, and the available information does not support attributing the outage to malicious activity.
As an affiliate, we earn on qualifying purchases.
Incident Review May Add Details
Users who still encounter errors should check Anthropic’s status page, retry authentication and confirm whether their application is using an affected interface or the operational API. The main recovery milestone has passed because Anthropic reported full restoration at 22:40 UTC.
The next substantive development would be a post-incident explanation describing the cause, affected systems and any corrective work. Until Anthropic publishes such an account, the confirmed record remains limited to the service updates and restoration notice issued during the outage.
Source: Anthropic
AI authentication and security devices
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Is Claude still down?
No. Anthropic said all services were restored by 22:40 UTC on August 16, 2026. Isolated user problems after that notice may require a new login or local troubleshooting.
Which Claude services were affected?
The confirmed disruption affected Claude.ai, Claude Code and Claude Cowork. Anthropic also reported degraded performance on platform.claude.com during the incident.
Was the Claude API affected?
The Claude API was listed as operational during the outage. The most serious confirmed impact involved user-facing services and authentication.
How long did the outage last?
Anthropic first reported the problem at approximately 21:58 UTC and announced restoration at 22:40 UTC, a span of about 42 minutes.
What caused the Claude outage?
The cause is not publicly confirmed. Anthropic has not said whether the incident resulted from capacity, infrastructure, authentication systems or another technical failure.
Source: Anthropic
