When exactly will Codex fix the recent slowdown and quality degradation?

Open 💬 9 comments Opened May 26, 2026 by GGBondBlueWhale
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Codex has felt noticeably slower and less capable over the past several days. The slowdown and quality degradation started over the weekend, and now it is already Tuesday, but the issue still does not appear to be fixed.

The main problems I am seeing are:

  • Tasks that used to finish much faster are now taking significantly longer.
  • The quality of the output has become noticeably worse, especially on coding and debugging tasks.
  • Some tasks now waste a large amount of time and usage, while still producing results that need to be reverted or redone.
  • As a $200/month Pro subscriber, this experience feels very disappointing and not worth the cost right now.

Codex is serving a global market, so it should be able to provide stable 24/7 operation. If users in California cannot reliably use Codex during normal daytime hours or over the weekend, what about users in the Eastern Hemisphere? Is there enough operational coverage during weekends and off-hours to monitor and maintain service quality?

This is not just a small inconvenience for paying users. Codex needs to meet basic expectations for stability, speed, and output quality. Could the team please provide a clear update on whether this slowdown and quality regression is known, whether it is being actively investigated, and when users can expect normal performance to be restored?

Please prioritize this urgently. Right now, the experience does not feel acceptable for a paid Pro user, and basic customer expectations are not being met.

View original on GitHub ↗

9 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #24431
  • #24422
  • #24549
  • #24553
  • #24585

Powered by Codex Action

boscoj2008 · 3 months ago

I’m in Tokyo and i can at least say the same. Codex feels like it started running on CPU power lately. Totally unacceptable to higher tier users.

duanshao-coco · 3 months ago

星期天之前还一直正常能使用的,最近的两天都是很慢很慢,我的Codex一直显示Working,然后不继续往下执行,导致我不知道是不是卡死了,还是它只是慢。

richardzzp · 3 months ago

看起来像是在排队思考,我5.5 xhigh fast,之前运行很流畅,现在都要等很久,哪怕是一个简单的任务。

xiecq · 3 months ago

从周一开始就这样了,今天一个小更新以为会修复,结果还是一直正在思考,根本用不了

richardzzp · 3 months ago

我尝试把fast模式关了,你猜怎么着,变快了。。。

joshp123 · 2 months ago

I'm seeing significant model quality degradation too. A few feedback IDs (if you can query by my account, you'll find many more)

019e8771-c8fd-7371-be91-34dccfa08ad4
019e88ac-5d8e-73a3-a101-84735a0fc85e

zhuxiwu995 · 2 months ago
我在东京,至少我可以这么说。最近 Codex 感觉像是开始过度依赖 CPU 性能了。这对高级用户来说完全无法接受。

cpu没占满,应该是软件优化没做好,整个codex的软件任务文件也不超过1个g,就开始卡了

lonardo · 15 days ago

+1 — seeing the same quality regression over the last 2 days.

Symptoms:

  • noticeably weaker instruction following
  • loses task context / needs repeated corrections
  • more thrashing and retries on tasks that used to be straightforward
  • higher token burn for worse results

This does not feel like normal variance. Happy to provide thread/feedback IDs if useful.