October 14, 2026 • Outage Desk • 3 min read

Another Night, Another Incident. Codex And ChatGPT Work Go Down Again.

Early Wednesday OpenAI confirmed elevated errors in Codex and ChatGPT Work, one day after its GPT 6.1 Sol incident. Users were reporting capacity errors before the status page moved.

An out of order sign, shown for illustration. Photo: Ville Säävuori, CC BY-SA 2.0, via Wikimedia Commons.

For the second night in a row, OpenAI's status page lit up for Codex and ChatGPT Work. Early Wednesday, October 14, the company confirmed elevated errors across both products, about a day after it closed its incident for degraded GPT 6.1 Sol performance.

What OpenAI posted

At 12:05 AM Pacific, OpenAI opened an incident titled "Degraded performance in Codex and ChatGPT Work." The first update read: "We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation."

More than two hours later, at 2:19 AM, the update was nearly the same: "We are still implementing the mitigation." The incident was marked resolved at 2:53 AM with the line "All impacted services have now fully recovered." OpenAI did not give a cause or say how many users were hit.

Less than half an hour later, at 3:18 AM, a separate incident opened for "limited availability" on two image models in the API, gpt-image-2.5-flare and gpt-image-2.5-sunburst. That one was resolved at 3:58 AM.

Users saw it before the incident opened

At 12:15 AM Pacific an r/codex user posting as NeoGokuTM wrote: "For the past hour, I've been constantly getting an error message in Sol 6.1. selected model is at capacity. please try a different model." That puts the trouble back to about 11:15 PM Tuesday, roughly 50 minutes before OpenAI's first update.

The same minute, another user posted a thread titled "It is a poorly hidden service outage at this point," listing "Constant model capacity errors, goals stalling, tps at snail speed." The post adds: "This should show be red on the service status but it is not." At 12:27 AM a third user asked "Codex down?" and wrote that all of their agents had stopped working about 30 minutes earlier.

At 1:38 AM, with the incident still open, a user posting the same capacity error asked which models were working, and wrote: "I've noticed GPT 6.1 Sol is the worst."

Slow, even when it is "up"

The complaints did not stop when the status page went green. At 3:14 AM a user who pays for both a Plus and a Pro plan wrote that it had been "about 2 weeks" since their last post about Codex being "painfully slow even with fast mode enabled," and that they "still don't see any real improvement." At 3:30 AM, more than half an hour after the resolution, another thread asked again: "Codex Down?"

A pattern, not a blip

This is the second Codex and ChatGPT Work incident in two days. The October 13 incident for GPT 6.1 Sol ran from 1:10 AM to 9:36 AM Pacific. Wednesday's ran almost three hours. Users have been reporting "at capacity" errors on the newest Sol model since the weekend, and only some of those hours ever appeared on the status page.

We will update this page if OpenAI explains what is causing the repeated errors.

Sources

Keep Digging

Homepage GPT 6.1 Sol Degraded, Oct 13 ChatGPT Status Tracker Real User Accounts Every Article On This Site

← Back to ChatGPT Disaster Homepage