Loading story…
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.
Track how attackers are adapting to this technology.
4 events from the most recent confirmed update back to the earliest known activity.
OpenAI publicly listed an incident under investigation involving elevated errors and degraded performance across 15 ChatGPT components and four Codex components. The company had not confirmed a root cause, mitigation timeline, affected regions, or attribution to a cyberattack or breach.
ChatGPT was reported down for many users at 14:20 UTC, with users reporting unloaded chats, message failures, stalled responses, and mobile-app issues. OpenAI acknowledged a further issue at 14:22 UTC; no root cause was publicly identified.
OpenAI recorded a ChatGPT Work Mode incident involving high error rates beginning at 12:04 AM UTC. The affected services were initially marked as recovered.
OpenAI’s status history listed elevated errors affecting ChatGPT Free and Go conversations.
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.
2 references tracked. Mallory keeps watching after this page renders.
Map 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.
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 patched a ChatGPT vulnerability that allowed sensitive conversation data and uploaded files to be exfiltrated through a covert DNS-based outbound channel in the platform's code-execution runtime. Check Point Research said a malicious prompt or backdoored custom GPT could abuse the isolated Python/Linux environment to leak user content without approval dialogs or visible warnings, and the same path could support bidirectional communication for remote shell access and command execution. OpenAI said it had already identified the underlying issue internally and fully deployed a fix on **February 20, 2026**; reports said there is no evidence of malicious exploitation. A separate OpenAI flaw in **Codex** also drew scrutiny after BeyondTrust Phantom Labs disclosed a critical command injection issue tied to GitHub branch names. The bug could let attackers inject commands, steal GitHub tokens, and potentially move laterally across shared repositories before OpenAI patched it on **February 5, 2026**. The disclosures underscore how AI assistants and coding agents can introduce new enterprise attack paths when outbound communications, runtime isolation, and input validation are not tightly controlled.
Jun 29, 2026
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.
Sep 4, 2026