You Pay $200 A Month. The Model Is "At Capacity."
Since Sunday night, ChatGPT Pro and Codex users say queued jobs are being rejected with a capacity error, while OpenAI's status page shows no incident.
A highway traffic jam, shown for illustration. Photo: Countryball_mys123, CC BY 4.0, via Wikimedia Commons.
OpenAI's status page read "All Systems Operational" on Monday afternoon, October 12, and its incident list showed nothing new since Friday, October 9. Paying ChatGPT and Codex users saw something else: a red error telling them the model they pay for is full.
"Selected model is at capacity"
The message reads "Selected model is at capacity. Please try a different model." Just before midnight Pacific on Sunday, October 11, a Codex user posting as NicholasVinen asked r/codex whether anyone else was getting it with Sol 6.1. "I just had a bunch of queued jobs rejected with this error message," the user wrote, adding that Sol 6.1 is so slow "that it takes hours to catch up with my list of requests and now I have to start again."
Half an hour later another r/codex user, Unfair_Bee_7429, posted under the same title: "I am a $200 pro subscriber and I have never seen this." The user asked why OpenAI offers so many models "if the flagship models are being rate limited."
A Pro subscriber says support went silent
At 7:11 AM Pacific on Monday, a ChatGPT Pro subscriber posting as ziodatahawno opened a thread on the OpenAI Community forum titled "Frequent Selected Model at Capacity Errors, Severe Decline in Model Quality, and Prolonged Lack of Response from Customer Support." The user describes "increasingly frequent" capacity errors along with "a noticeable and severe decline in model quality," and says the trouble shows up in "reasoning, instruction following, and complex tasks."
The user says they sent support everything it asked for: conversation links, timestamps, screenshots and model settings. Then, "customer support simply stopped responding. No explanation." The post adds: "I'm still paying for my Pro200 subscription every day while experiencing these issues." The user also says they suspect requests are being quietly routed to a cheaper model. That is the user's suspicion, not something OpenAI has confirmed.
Slow, then slower
The capacity errors land on top of a weekend of speed complaints. On Sunday at 12:50 PM Pacific, an r/codex user asked whether OpenAI had nerfed the speed: "Basic tasks that would take 3 4 mins are taking 20+ mins." On Monday another user started a thread asking whether anyone else was seeing "extremely slow response times and code generation with OpenAI Codex," noting that people on Pro were reporting the same thing.
What the status page says
As of Monday afternoon Pacific, status.openai.com lists no incident for capacity errors or slow Codex responses on October 11 or 12. The most recent entries are from October 9: delayed Compliance API cost data, some ChatGPT content missing on Android, and workspace admins unable to manage plugins. All three are marked resolved.
For people paying up to $200 a month, "try a different model" is not much of an answer. We will update this page if OpenAI posts an incident or explains the errors.
Sources
- r/codex: "Selected model is at capacity. Please try a different model." (October 11, 2026)
- r/codex: "Selected Model is at Capacity" (October 12, 2026)
- OpenAI Community forum thread (October 12, 2026)
- r/codex: "Speed Nerf" (October 11, 2026)
- OpenAI status page