Security

Claude Went Down Worldwide for 42 Minutes on the Morning of August 17.

On the morning of August 17, Claude suffered a 42-minute global outage that began as authentication errors and spread to degraded performance. Here's Anthropic's official timeline and how to respond in practice.

· Huuush

Claude Went Down Worldwide for 42 Minutes on the Morning of August 17

Key takeaways

  1. 1The August 17 outage began with authentication issues and widened to degraded performance on claude.ai and platform.claude.com.
  2. 2According to Anthropic's status page, a fix was deployed at 07:22 KST and services returned to normal between 07:34 and 07:40 KST.
  3. 3The cause and steps to prevent a recurrence weren't disclosed, so work environments should prepare with the status page and retry and timeout handling.
Still life photo of a smartphone with a dark screen and a red warning light on a dark navy background

7:25 AM: "Claude Won't Open"

On the morning of August 17, 2026, Claude stopped working worldwide at the same time.

A post from the news account The Spectator Index reading "BREAKING: Claude outage for many users across the globe" drew more than 380,000 views.

Reactions piled up: logins failing, answers cutting off, and screens freezing in the middle of coding work.

42 Minutes From Authentication Errors to Degraded Performance

According to Anthropic's official status page, the outage began at 21:58 UTC on August 16, 2026 (6:58 AM KST on August 17).

The first notice was "authentication issues for some users of claude.ai, Claude Code, and Claude Cowork."

Four minutes later, at 22:02 UTC (07:02 KST), Anthropic widened the scope and officially acknowledged "degraded performance on claude.ai and platform.claude.com."

A fix was deployed at 22:22 UTC (07:22 KST), and all services were confirmed back to normal between 22:34 and 22:40 UTC (07:34 to 07:40 KST). The total outage lasted about 36 to 42 minutes.

Anthropic did not disclose the specific cause.

Time (KST)Event
06:58Outage begins: notice of investigation into authentication errors on claude.ai, Claude Code, and Claude Cowork
07:02Scope widens: degraded performance on claude.ai and platform.claude.com officially acknowledged
07:25The Spectator Index "global outage" post spreads (380,000+ views)
07:22Fix deployed
07:34 to 07:40All services confirmed back to normal

Why Does a Different Account Always Post the "Breaking News" First?

As with this outage, when Claude goes down, X posts from news accounts and individuals spread before the official status page does.

In fact, "Claude is down" breaking-news posts went up from multiple accounts at the same time during this outage.

That's because Anthropic's status page (status.claude.com) updates its notices a few minutes late, while users feel the problem instantly.

This isn't the first major Claude outage. In March 2026, there was a separate outage with about 2,000 simultaneous connection error reports on Downdetector.

What You Can Do Now to Prepare

  • If you depend on Claude Code or Cowork for work, bookmark status.claude.com so you can find the cause faster.
  • If your product integrates the API, building in short retries and timeout handling by default reduces the outage users feel in moments like this.
  • Outages like this one often end within 30 to 40 minutes, but since the cause hasn't been disclosed, checking the status page yourself is the most reliable way to know whether it recurs.

Anthropic hasn't separately disclosed the root cause or the steps to prevent a recurrence, so these are not officially confirmed.

Frequently asked questions

When did the Claude outage start and when did it recover?
According to Anthropic's status page, the outage began at 21:58 UTC on August 16, 2026, which is 06:58 KST on August 17. All services were confirmed back to normal between 07:34 and 07:40 KST.
Was the cause of this Claude outage disclosed?
No. The Anthropic status page and reports cited in the article did not disclose a specific root cause.
How can you prepare for outages when using Claude Code for work?
The article suggests bookmarking status.claude.com and, for products that use the API, building in short retries and timeout handling by default.

Related articles