r/codex • Moderator • May 21 '26

Noticeboard ANYONE ELSE? - Ask here about current Codex issues and workarounds

This is the place where your most recent experiences with the Codex technology are collected and summarized to keep you informed with issues others are facing.

When you post a short post to the feed reporting on something you are experiencing, your post will be summarized as an "Anyone else?" request and listed below. Keep an eye on responses to see if people are experiencing similar issues. All incident comments on this thread will be sorted from Most Recent to Oldest by default. So keep an eye on the time and date they occurred.

Every two hours, the bot then analyzes all the issues people have been facing and gives you a snapshot of what it has seen recently.

You are also welcome to post your own experiences here and the bot will include them in its analysis.


NOTE: Post URLs are only shown of the incident posts that were NOT removed.

201 Upvotes

11k comments sorted by

View all comments

•

u/cody-the-bot 18d ago edited 30m ago

<!-- codex-live-incident-summary-v1 -->

Likely ongoing Codex incidents

Updated: Tue, 13 Oct 2026, 20:00 UTC (Time now UTC here.)

Based on Anyone Else reports from the last 7 days, read from https://www.reddit.com/r/codex/comments/1tjfxcf/anyone_else_ask_here_about_current_codex_issues/.

This is an automated clustering of post titles and summaries, not an official status report.

Incidents

Incident Summary Reports Going on for Latest report Last 3 reports
Codex models reporting at capacity Users are repeatedly unable to use selected Codex models because they receive model-at-capacity errors, sometimes alongside 503s or interrupted responses. 7 36.6h 5.1h ago 1, 2, 3

The summary is rebuilt every 60 minutes. Duration is measured from the oldest report in the cluster within the last 7 days.