Claude outage on April 13 hit logins, not a hidden platform-wide collapse

Anthropic’s Claude did suffer a real disruption on April 13, 2026, but the public record does not support the claim that the company left its status page at “All Systems Operational” throughout the incident. Anthropic’s official status history shows a logged incident titled “Claude.ai down,” with elevated login errors affecting Claude.ai and Claude Code between 15:31 and 16:19 UTC.

That detail matters because it changes the framing of the story. This was not a fully unacknowledged outage across every Claude surface. Based on Anthropic’s own incident log, the confirmed issue centered on login problems for Claude.ai and Claude Code, not a broad confirmed failure of claude.ai, the API, and Claude Code all at once on April 13.

BEST SPRING 2026 DEALS

Editor's Choice

Private Internet Access

Access content across the globe at the highest speed rate.

70% of our readers choose Private Internet Access

70% of our readers choose ExpressVPN

ExpressVPN

Browse the web from multiple devices with industry-standard security protocols.

Nord VPN

Faster dedicated servers for specific actions (currently at summer discounts)

Anthropic marked the issue as resolved at 16:35 UTC on April 13 after first posting an investigation update at 15:40 UTC and then an identified update at 16:16 UTC. Public live coverage from Tom’s Guide also reported that Anthropic acknowledged the outage on its status page during the event.

What Anthropic actually confirmed

Anthropic’s status history says the incident caused “elevated errors on login for Claude.ai and Claude Code” and gives a specific impact window of 15:31 to 16:19 UTC. The same entry does not say the Anthropic API was broadly down during that April 13 incident.

That does not mean users imagined wider problems. Community reports and news coverage described failed chats, blank responses, and other instability around the same period. But the cleanest confirmed version is narrower: Anthropic officially acknowledged a login-related outage affecting Claude.ai and Claude Code, then resolved it within roughly an hour.

The sample you shared overstates one important point by saying Anthropic’s status page continued to show all systems operational during the disruption. Anthropic’s own incident history shows the opposite. Once the event was underway, the company posted an active incident for April 13.

Why users felt this fit a bigger pattern

Even though the April 13 write-up overshoots in places, it points to a real broader issue: Claude had multiple incidents in early April. Anthropic’s history shows outages or elevated errors on April 6, April 7, April 8, April 10, April 13, April 14, and April 15, with additional model-specific problems on April 16.

Some of those incidents were short. Others affected authentication, Claude.ai, Claude Code, or specific models. On April 15, for example, Anthropic logged “Elevated errors on Claude.ai, API, Claude Code,” and that event explicitly affected the API as well as login to Claude.ai and Claude Code.

So the stronger version of the article is not “Anthropic hid an outage.” It is that Claude experienced a string of real availability issues in April, and the April 13 login outage landed in the middle of that run, which likely made users more sensitive to even brief failures.

What happened around April 13

Source: Anthropic status history.

Why this matters for developers and teams

Short login outages can still cause real disruption, especially for teams that depend on Claude Code or web access to Claude during working hours. If authentication fails, users may lose access even when some backend systems still function. Anthropic’s own April 15 status notes showed this clearly, with the API recovering before Claude.ai login fully stabilized.

That split matters for enterprise users. A service can look partly alive while important workflows remain broken. In practice, that means developers and operations teams need fallbacks, retries, and an alternate path when Claude login or model access becomes unstable. This is an inference based on the incident pattern Anthropic logged across multiple dates.

The broader concern is not one outage by itself. It is the frequency. Anthropic’s public incident history for April shows repeated service events across chat, login, Claude Code, specific models, connectors, and admin APIs.

FAQ