Codex Outages Keep Recurring for OpenAI in the Weeks After DevDay

OpenAI used its September DevDay to present Codex as the center of its agentic developer strategy. In the weeks since, the product's public record has filled with incidents, capacity errors and billing complaints. The tool is clearly in demand. The open question is whether OpenAI can make it dependable enough to match the pitch.

What happened

The trouble started almost immediately. A GitHub issue opened on the official Codex repository gathers a wave of user reports beginning with the September 8, 2026 DevDay and GPT-6 Astra launch. It describes Codex as effectively unusable for stretches of hours because of capacity and server-overload failures. 1 The most common message told users that the selected model was at capacity and suggested switching models. 1 The same issue notes that frustration over the five-hour usage window surfaced at the top of replies to OpenAI's launch post. 1

The problems did not end with the launch-week rush. On October 5, OpenAI's status page posted an incident for elevated error rates in Codex Cloud. The company said it had identified the problem and was working on a mitigation, although no components were marked as affected. 3

The status history for October 13 shows how many separate failures can land on one day. 4 Entries that day include:

• Degraded performance in GPT-6.1 Sol Codex and Work mode
• Failed and delayed turns for the Dot agent
• A bug that stopped Dot in Codex from creating new threads
• A desktop-app defect that blocked new ChatGPT Work threads and required an updated release for Linux, macOS and Windows
• A separate spike in errors across ChatGPT, Codex and the API, including the Agents API 4

The page also logs errors touching image generation, Spaces and Pages, Work mode, and platform login and administration APIs. 4

Usage limits make outages more expensive

Under a usage-capped subscription, an outage costs more than lost time. It can also use up the allowance customers have paid for.

Developers on r/ChatGPTPro report that Codex Cloud and ChatGPT Work still lose runs mid-task and drop MCP connections during long sessions. 5 Failed tasks also count against weekly allowances, and there is no checkpoint to resume from. One user said a single task consumed two full usage-reset credits. 5

Complaints on the OpenAI community forum run along the same lines:

• A subscriber on the $200-a-month Pro 20x plan said they used up a full weekly quota in under two days. 2
• Another bought 2,500 extra credits and watched them disappear within two hours, while the analytics page showed no usage events. 2
• A longtime user said their effective weekly allowance had fallen to roughly a tenth of what it was a month earlier, with limits now triggering at around 38 million tokens. 2

OpenAI's response has combined explanation with goodwill gestures. Its Codex engineering lead blamed a practice called sub2api for many of the limit complaints. Hours later, the company marked Codex passing 20 million active users by giving every subscriber a banked usage reset. 2 Memeburn reports that this is at least the third time in 2026 that usage complaints have forced an OpenAI response, after similar episodes in March and June. 2

Where accounts differ

OpenAI frames the limit problem mainly as abuse by sub2api users. 2 Developers describe something closer to accounting and reliability failures: credits draining with no recorded events, and allowances spent on runs that crashed. 25 These explanations are not mutually exclusive. Still, the reports of usage disappearing without any logged events are hard to explain as third-party misuse alone.

The status page has limits of its own. OpenAI notes that its availability figures are aggregated across tiers, models and error types, and that individual customers' experience may vary. 3 The Codex Cloud incident that listed no affected components shows how official dashboards can make problems look smaller than users experience them. 3

There is also a capability gap alongside the stability issues. According to the Reddit discussion, the Codex Cloud sandbox has no interactive shell, SSH or computer use, and works only with GitHub. That rules out runtime or hardware-level work despite OpenAI's cloud-first messaging. 5

The takeaway

The overall picture is a product growing faster than its infrastructure and billing systems can support. The 20-million-user milestone 2 alongside repeated capacity errors 1 suggests demand is outpacing compute. The cluster of agent-specific failures, including Dot, Work mode and the Agents API 4, suggests the newest features are the least stable.

For teams evaluating Codex, the Reddit thread's practical advice is sound: test Codex Cloud on low-stakes tasks before trusting it with production workflows. 5 Until failed runs stop counting against quotas and usage accounting can be verified, the subscription caps carry as much risk as the outages themselves.