codex - 💡(How to fix) Fix GPT-5.5 Fast mode feels like Standard speed while using increased plan usage [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19241Fetched 2026-04-24 05:58:10
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×1unlabeled ×1

I am seeing a noticeable speed degradation with GPT-5.5 in Codex even though Fast mode is enabled.

Earlier today, around 3 PM ET when GPT-5.5 first became available for me, Fast mode felt genuinely fast and clearly matched the expected Fast experience. However, later in the evening around 7-8 PM ET, after more users appeared to receive access to GPT-5.5, the speed became noticeably slower.

It is not completely unusable, but it no longer feels like the Fast speed I experienced earlier today. It feels much closer to Standard speed.

Root Cause

I am seeing a noticeable speed degradation with GPT-5.5 in Codex even though Fast mode is enabled.

Earlier today, around 3 PM ET when GPT-5.5 first became available for me, Fast mode felt genuinely fast and clearly matched the expected Fast experience. However, later in the evening around 7-8 PM ET, after more users appeared to receive access to GPT-5.5, the speed became noticeably slower.

It is not completely unusable, but it no longer feels like the Fast speed I experienced earlier today. It feels much closer to Standard speed.

RAW_BUFFERClick to expand / collapse

Summary

I am seeing a noticeable speed degradation with GPT-5.5 in Codex even though Fast mode is enabled.

Earlier today, around 3 PM ET when GPT-5.5 first became available for me, Fast mode felt genuinely fast and clearly matched the expected Fast experience. However, later in the evening around 7-8 PM ET, after more users appeared to receive access to GPT-5.5, the speed became noticeably slower.

It is not completely unusable, but it no longer feels like the Fast speed I experienced earlier today. It feels much closer to Standard speed.

Environment

  • Product: Codex desktop app
  • App version: 26.422.21459 (2049)
  • Model: GPT-5.5
  • Intelligence level: Extra High
  • Speed setting: Fast
  • Approximate time observed: April 23, 2026, around 7-8 PM ET
  • Comparison point: April 23, 2026, around 3 PM ET, shortly after GPT-5.5 became available

What happened

Fast mode is enabled, so usage is being charged as Fast / increased plan usage. However, the actual experience feels much closer to Standard speed.

As one recent example, I ran a very simple task and it took about 7 minutes 49 seconds. Based on how GPT-5.5 Fast behaved earlier today, I would have expected a small task like this to finish in roughly 5-6 minutes or less.

Expected behavior

If Fast mode is enabled and charged with increased plan usage, the actual response speed should remain consistently faster than Standard mode.

If server load is too high to maintain stable Fast performance, I think the Fast usage cost should be reduced, paused, or adjusted accordingly. Otherwise, users are paying the Fast usage cost while effectively receiving Standard-like speed, which feels unfair.

Request

Could the team please investigate whether GPT-5.5 Fast mode is being degraded under higher server load or increased rollout traffic?

I would appreciate it if the team could seriously look into this and consider a fair handling of Fast usage charging when the backend cannot consistently provide Fast-level performance.

<img width="1116" height="748" alt="Image" src="https://github.com/user-attachments/assets/59145254-b1dc-4f5e-b786-9270828d1a57" /> <img width="1694" height="262" alt="Image" src="https://github.com/user-attachments/assets/10f03599-1048-4edd-9fbc-94e785ea4745" />

extent analysis

TL;DR

The most likely fix is for the team to investigate and adjust the server load management to ensure consistent Fast mode performance in GPT-5.5.

Guidance

  • Investigate server load and its impact on GPT-5.5 Fast mode performance to determine if high traffic is causing the speed degradation.
  • Consider implementing load balancing or scaling to maintain stable Fast performance under increased traffic.
  • Review the current pricing model for Fast usage and consider adjusting it to reflect actual performance when server load is high.
  • Monitor performance metrics, such as response times, to identify patterns and optimize server resource allocation.

Notes

The issue seems to be related to server load and traffic, but without more technical details, it's difficult to provide a specific solution. The team should investigate and gather more data to determine the root cause and implement an effective fix.

Recommendation

Apply workaround: The team should consider temporarily adjusting the Fast usage charging or providing refunds to users who experienced slower performance until the issue is resolved, to ensure fair handling of Fast usage costs.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

If Fast mode is enabled and charged with increased plan usage, the actual response speed should remain consistently faster than Standard mode.

If server load is too high to maintain stable Fast performance, I think the Fast usage cost should be reduced, paused, or adjusted accordingly. Otherwise, users are paying the Fast usage cost while effectively receiving Standard-like speed, which feels unfair.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix GPT-5.5 Fast mode feels like Standard speed while using increased plan usage [1 comments, 2 participants]