I'm a paying ChatGPT Pro subscriber. Since around September 17, 2026, recurring technical failures have repeatedly disrupted my work. It's now October 13, and I still have conversations and projects I cannot reliably access or continue.
Here is what the problem looks like in practice:
- Long-running conversations inside Projects suddenly fail to load. Sometimes I cannot reopen the very thread where I was working.
- GPT-6 Pro and GPT-5.6 Pro responses or longer tasks are interrupted or fail before completion, making it difficult to resume work from the same point.
- Reloading or retrying may briefly restore access, only for another failure to interrupt the next step. Each failure costs time spent reconstructing context, locating previous results, or recreating work.
- My support requests have yet to produce a lasting solution or a clear plan for restoring access to the affected conversations.
OpenAI's own incident history shows how often related parts of the paid service have experienced problems during this period:
- **September 17:** ChatGPT Work tasks could fail to start or run.
https://status.openai.com/incidents/01M2RC0WHGTX8EHDH7D60JJ7FC
- **September 22:** Elevated ChatGPT Work error rates across Plus, Pro, Business, Enterprise, and Education plans.
https://status.openai.com/incidents/xqj8tm81
- **September 23:** Elevated conversation errors affecting Plus and Pro subscribers.
https://status.openai.com/incidents/01M36RMC01ZFWQ861WYJKC4XE1
- **September 29:** A feature rollout overwhelmed shared network-connection capacity. OpenAI's postmortem says some conversations and tasks could not start, resume, or finish.
https://status.openai.com/incidents/01M3Q4RK1SM4EMK445GGPG7C0N/write-up
- **September 30:** Another official incident recorded elevated error rates for ChatGPT Pro and Plus conversations.
https://status.openai.com/incidents/01M3RDNY37CAPQGRKPBVMNRT4K
- **October 5–6:** OpenAI recorded further errors involving conversations, Work mode, and several other ChatGPT services.
https://status.openai.com/incidents/01M46G248GGHV9RSAJE82BZY1X
https://status.openai.com/incidents/01M47HC9SGHGFPBN44KGC6SKAQ
- **October 8:** OpenAI acknowledged errors affecting conversations, Work, and GPTs for some users in the Asia-Pacific region.
https://status.openai.com/incidents/616df649
These are separate officially recorded incidents, with different possible causes. The ongoing customer experience matters too. On October 9–12, other users were still reporting inaccessible chats, HTTP 429 "Too Many Requests," interrupted response streams, and stuck Work sessions, including after earlier incidents were marked resolved:
https://www.reddit.com/r/ChatGPTcomplaints/comments/1x1g8el/chatgpt_errors_since_september_27_is_anyone_else/
https://community.openai.com/t/is-anyone-else-experiencing-recurring-chatgpt-loading-failures-stream-errors-and-stuck-tasks/1404071
A status page saying "resolved" should describe a real recovery for the people affected. For some of us, the same practical failures keep returning. We pay for a service that we need to be able to use consistently, especially when our work depends on existing conversations and their accumulated context.
**I propose that affected paid subscribers issue a joint public statement asking OpenAI to:**
Explain the recurring conversation-loading, streaming, and project-access failures, and identify which issues are still under investigation.
Deliver a lasting fix, restore access to affected conversations wherever possible, and publish meaningful progress updates.
Provide case-specific technical support for documented failures, including escalation and clear follow-up rather than repeated generic troubleshooting.
Offer fair monetary compensation or billing credits for paid features that were materially unusable, while allowing subscribers to keep their existing plans active.
I want to keep using ChatGPT Pro. I also expect a company charging premium subscription fees to take responsibility when core functionality repeatedly fails over several weeks.
**If you're affected, please share:** your plan, when the problems started, the error messages or symptoms, whether conversations recovered, how much work was disrupted, and what support actually did. Keep private conversation links, payment details, tokens, and identifying information out of public comments.
Would you support a joint statement demanding a reliable fix, a transparent explanation, and meaningful compensation for affected paying users?