JournalArta
Monday, August 17, 2026 · JakartaS&P 7,785.76 ▼0.17%USD/IDR 17,831 ▼0.18%Subscribe
JournalArta
Global Edition
beyond headlines
Advertisement
Technology · AI

Claude AI Services Restored Following 35-Minute Global Infrastructure Outage

Anthropic has restored full operational functionality to Claude.ai and platform.claude.com API services following a 35-minute global outage. Read the technical…

By Elena Vance
August 16, 20262 min read
Claude AI Services Restored Following 35-Minute Global Infrastructure Outage
Claude AI Services Restored Following 35-Minute Global Infrastructure Outage

SAN FRANCISCO — Anthropic confirmed Monday that all core infrastructure supporting its flagship artificial intelligence platform, Claude, has returned to full operational status following a brief but widespread 35-minute service disruption.

Live telemetry from Anthropic’s official status portal (status.claude.com) indicates that both the web conversational portal (claude.ai) and developer API services (platform.claude.com) are functioning normally, with error rates and response latencies returning to baseline metrics across all global regions.

Incident Timeline and Resolution Window

According to Anthropic’s system incident log, automated monitoring systems first flagged elevated error rates at 22:07 UTC. The company immediately classified the disruption as a "Major Impact" event after users and automated enterprise systems reported connection failures.

The incident resolution progressed along the following operational timeline:

Advertisement
  • 22:07 UTC: Engineering teams initiate critical incident response procedures following spike in HTTP 500 errors and prompt timeouts.
  • 22:22 UTC: Operations personnel isolate a routing database bottleneck within the API authentication cluster and deploy hotfix routing patches.
  • 22:42 UTC: System telemetry confirms traffic normalization across all endpoints, and Anthropic updates global status flags to "All Systems Operational."

In total, core service degradation lasted 35 minutes before failover protocols successfully absorbed residual queue backpressure.

Technical Root Cause Analysis

Preliminary engineering findings indicate that the outage was triggered by an acute traffic imbalance across Anthropic’s primary authentication gateway database. The resulting queue backpressure caused application servers to prematurely drop connection requests, surfacing intermittent HTTP 500 errors and gateway timeout messages to connected clients.

Infrastructure teams resolved the bottleneck by re-routing inbound API requests to redundant gateway clusters and reallocating memory pools dedicated to prompt state management.

Enterprise Workload Recovery

Anthropic assured corporate partners and developers that no user conversation histories or proprietary API data were compromised during the disruption. Third-party software integrations and automated enterprise agents that rely on Claude models have resumed normal operation.

The company stated it will release a formal post-mortem report detailing long-term architectural enhancements to prevent similar database bottlenecks during future peak-traffic periods.

Advertisement
Advertisement