openai / openai/codex

Not happy with under-performing service

Open
#43,466 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug model-behavior performance
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

To OpenAI Customer Support:

I am formally reporting serious and repeated performance failures affecting my paid ChatGPT Plus subscription, for which I pay $20 per month. I am also requesting meaningful compensation, such as a subscription credit, refund, or extension of service.

On September 7, 2026, a single instruction intended for Codex took approximately eight minutes to process, merge, display, and finally become available in copy-ready form. During that incident:

Short messages took abnormally long to process.
ChatGPT appeared to disappear or remain working without providing a timely response.
ChatGPT incorrectly stated that instructions had been sent before I had actually sent them.
ChatGPT failed to bring a requested paste-ready instruction forward, forcing me to ask again.
The delays directly interrupted and materially slowed active development work on my Howard local-assistant project.

This is not an isolated eight-minute inconvenience. Throughout my use of ChatGPT, I have repeatedly experienced slowdowns, periods when the service became effectively unusable, lost work time, and unnecessary repetition. I cannot precisely quantify the cumulative loss because many earlier incidents were never formally recorded. Nevertheless, the accumulated disruption has been substantial, and recently it has occurred on a near-daily basis.

For approximately the last four or five days, I have also observed frequent ChatGPT updates, including what was described as an upgrade. I understand that updates do not prove that OpenAI has identified a particular defect, but the timing reinforces my concern that significant reliability work may be underway while I continue receiving degraded paid service.

During the September 7 session, an additional unexplained event occurred: a photograph of my wife’s dog—used as wallpaper on her separate computer—appeared as an attachment in my ChatGPT conversation even though I did not select, attach, or send that photograph. A local security inspection found no evidence that my Dell computer had been compromised and found no matching recent image in the inspected local locations. I want OpenAI to investigate how this attachment entered the conversation and whether it came from account storage, application behavior, synchronization, an interface defect, or another source.

I recognize that occasional technical problems can occur. However, I am not using a free account or the lower-priced $8 plan. I am paying $20 each month for ChatGPT Plus and believe that the reliability and usable value delivered have fallen materially short of what a paid subscriber should reasonably expect!

I request:

Investigation of the repeated severe delays and periods of unusability associated with my account and sessions.
Investigation of the unexplained photograph attachment.
Correction of the underlying reliability problems.
An explanation of any findings relevant to my account.
Appropriate compensation for the estimated cumulative loss of paid service and productive time, whether through a refund, account credit, complimentary subscription extension, or another meaningful remedy.

Please preserve this complaint as a formal service-quality and account-security report. I would appreciate a substantive response rather than general troubleshooting language.

Sincerely,

Dennis Werda
ChatGPT Plus subscriber
September 7, 2026

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is identified. Treat this as a service-quality and account-security report rather than a scoped repository task; the payload provides no code-level completion condition or reproducible test.

Written by the indexing model from the issue text.

Assessment

Domain
backend, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.