"User across multiple subscription plans may be unable to start or continue tasks in ChatGPT Work. We are continuing to work on a mitigation," OpenAI said in its latest update.
OpenAI's acknowledgement and timeline
OpenAI first acknowledged a partial outage affecting ChatGPT Work at approximately 11:04 AM ET on Monday, August 31. The company posted the incident on its status page and advised users that elevated latency had been observed for the impacted services. By 12:02 PM ET the same day, the outage remained ongoing and OpenAI reiterated that users across multiple subscription plans might be unable to start or continue tasks while engineers work on a mitigation.
Services and subscriber tiers affected: ChatGPT Work and Plus
The disruption is centered on ChatGPT Work functionality. OpenAI said users are experiencing elevated errors across the impacted services, and called out Plus subscribers as being particularly affected because Work mode is currently unavailable for some of them. The company’s messaging describes the problem as a partial outage rather than a full service interruption, but emphasizes that the impairment prevents normal Work-mode operations for a subset of customers.

The cyber insurance questionnaire just landed. Now what?
SOC 2, HIPAA, insurance renewals - someone has to own security strategy. Nubivance provides fractional CISO leadership without the full-time salary.
Get a security leadUser experience: elevated latency, errors, and halted tasks
Reported symptoms are elevated latency and increased error rates. OpenAI’s status updates note that customers may be unable to start new tasks in ChatGPT Work, and in some cases may not be able to continue tasks that were already running when the incident began. The vendor’s messaging explicitly links the elevated errors and latency to the inability to initiate or maintain Work-mode sessions for affected accounts.
OpenAI's response and mitigation status
OpenAI acknowledged the incident on its status page and said it has identified elevated errors across the impacted services. The public updates make clear that the company is working on a mitigation but had not declared the issue resolved as of the last posted timestamp. The sequence of statements—initial acknowledgment at ~11:04 AM ET, identification of elevated errors, and an update at 12:02 PM ET confirming the outage remained ongoing—frames the event as an active operational incident for which a fix was still being pursued.
What this means for technologists, enterprises, and end users
- Technologists and security teams: expect interruptions to automated workflows that rely on ChatGPT Work. Elevated latency and error states can surface in monitoring systems as failed tasks or timeouts; teams should watch for tasks that fail to resume and route diagnostics to OpenAI’s status channel as necessary.
- Affected enterprises and procurement leaders: organizations using Work-mode capabilities should prepare for temporary outages in task execution and may need to pause time-sensitive operations that depend on continuous conversational workflows until OpenAI’s mitigation is in place.
- End users and the general public: Plus subscribers and others using Work mode may find they cannot start or continue tasks. If you encounter errors or increased latency, the company’s status page is being used for real-time updates and OpenAI has signaled it is working on a fix.
The incident underscores a familiar dynamic: even partial outages focused on a single mode or subscription tier can cascade into visible disruption for customers who have integrated that mode into daily workflows. OpenAI’s public timeline—an initial acknowledgment at 11:04 AM ET and a follow-up at 12:02 PM ET confirming the outage remained ongoing—offers a narrow but concrete record of the company’s early incident handling and its ongoing mitigation effort.
Original story: https://www.bleepingcomputer.com/news/artificial-intelligence/openai-confirms-chatgpt-outage-as-users-report-errors/




