Loading story…
OpenAI, Anthropic and xAI suffered near-simultaneous service disruptions that affected ChatGPT, Codex, Claude and Grok. Anthropic users experienced elevated errors, stalled responses and failed web and API requests, disrupting Claude Code and other API-dependent workflows; its Console remained operational and Claude for Government was not identified as affected. OpenAI said its incident began with a routing error, while SpaceX attributed Grok's disruption to an outage at its Memphis compute center.
The providers reported restoration within roughly two to three hours, and no corresponding outages were reported by AWS, Microsoft Azure, Google Cloud or Cloudflare. The overlapping failures underscored the operational impact of relying on AI services for production workflows, including risks from single-provider dependence, vendor concentration and dependencies on shared infrastructure.
Track how attackers are adapting to this technology.
8 events from the most recent confirmed update back to the earliest known activity.
xAI reported the Grok incident fixed at 10:05 a.m. Pacific Time. SpaceX said systems at its Memphis compute center had been restored and were functioning normally.
Anthropic reported that the Claude incident was fixed at 9:16 a.m. Pacific Time after disrupting web, API, and Claude Code workflows.
OpenAI marked its incident affecting ChatGPT and Codex as resolved at 9:15 a.m. Pacific Time.
A routing error beginning at about 7:43 a.m. Pacific Time caused elevated errors across OpenAI's ChatGPT and Codex services.
Anthropic expanded its affected-model list to include Mythos/Fable 5.1, Mythos/Fable 5, Opus 5, Opus 4.8, and Opus 4.6.
Anthropic reported that it had identified the underlying cause of the Claude service disruption and was working on a fix.
Anthropic posted an Investigating notice for elevated request errors affecting Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5. The Claude web service and API were experiencing a partial outage.
xAI reported issues affecting Grok amid the near-simultaneous AI-provider disruptions. SpaceX later attributed the Grok impact to an outage at its Memphis compute center.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
3 references tracked. Mallory keeps watching after this page renders.
itpro.com
Open sourcestatus.claude.com
Open sourcecryptika.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Anthropic's Claude platform suffered another service disruption that caused elevated `529 Overloaded` errors and partial outages across **claude.ai**, the **Claude API**, **Claude Code**, and **Claude Cowork**. Anthropic first reported the incident at 05:06 UTC and said it had identified the root cause by 05:27 UTC, but remediation was still in progress past 06:42 UTC with no full recovery confirmed. The disruption affected several major models, including **Claude Mythos 5**, **Claude Fable 5**, **Claude Opus 5**, and **Claude Opus 4.8**, disrupting enterprise and developer access to production AI workflows. Anthropic said **Claude Console** and **Claude for Government** were not affected, while reporting around the incident pointed to a broader pattern of recurring Claude instability and capacity-related service issues during 2026.
Aug 24, 2026
OpenAI confirmed a global outage that prevented many users from logging into **ChatGPT**, creating new accounts, loading current or previous conversations, and sending messages. The disruption began around 8 p.m. EDT and affected users in multiple regions, including the United States and Europe, with OpenAI acknowledging the incident on its status page and saying it had identified login-related issues and was working on mitigation. Reports said the outage lasted about an hour for many users, though OpenAI initially indicated the incident was still ongoing as engineers responded. The disruption also reportedly affected OpenAI's **Codex** platform and parts of the OpenAI API, while other reporting said the impact appeared largely limited to the consumer-facing ChatGPT service rather than a broader API failure that would have caused wider downstream business disruption.
Aug 20, 2026
OpenAI is investigating elevated error rates and degraded performance affecting **ChatGPT** and **Codex**. Users reported conversations failing to load, messages not sending, delayed or missing responses, unexpected errors, and interrupted sessions, with mobile users on Android and iPhone among those reporting problems. OpenAI’s status page identified 15 ChatGPT components and four Codex components as affected. The disruption follows a September 3 `ChatGPT Work Mode High Error Rates` incident that OpenAI initially marked recovered, while additional user reports and a further issue continued. OpenAI has not disclosed a root cause, affected regions or features, mitigation timeline, or evidence linking the incident to a cyberattack, data breach, infrastructure failure, or third-party dependency.
Sep 3, 2026