OpenAI users faced significant service disruptions on Friday evening,primarily affecting ChatGPT and Codex. The outage, which began around 6:55 p.m. EDT, was characterized by widespread authentication errors across multiple platforms.
The "Unexpected status 401" error blocking user access
The technical nature of the outage centered on a specific authentication failure that prevented users from interacting with AI models. Users reported receiving an "Unexpected status 401: Incorrect API key" message, which effectively blocked the ability to start or continue conversations. In web development, a 401 error typically signifies that a request lacks valid authentication credentials, making this particular error message highly disruptive for those relying on stable API access.
According to the report, this error was not merely a minor glitch but a primary symptom that paralyzed core functionalities. Because the error specifically cited an "incorrect" key, it created confusion for developers and casual users alike, who had not made any changes to their existing credentials or account settings.
Disruption across ChatGPT web and mobile interfaces
OpenAI's service disruption on Friday evening impacted both the web-based ChatGPT interface and its mobile applications. The report notes that while the severity of the issue appeared to vary between individual accounts , the disruption was widespread enough to be felt across the entire user base.
A sharp spike in reports on Downdetector confirmed that the outage was not an isolated incident for a small group of users. While some users experienced intermittent recovery, the service remained unstable for a significant period, affecting the accessibility of both the ChatGPT conversational interface and the Codex coding model.
OpenAI's development of a Codex mitigation strategy
OpenAI has officially acknowledged the disruption on its dedicated status page to inform its global user base. The company is currently investigating the root cause of the errors, with a specific focus on the issues affecting Codex users.
As the report states, a mitigation strategy is currently being developed by OpenAI engineers to restore full service. The company's response suggests that the issue is being treated as a high-priority technical failure , though a specific timeline for a total resolution has not yet been provided to the public.
The fragility of the API-driven developer ecosystem
The sudden instability of OpenAI's services highlights the growing dependency of the global tech sector on a small number of large-scale AI providers. when ChatGPT or Codex experiences downtiime, the impact extends far beyond individual chat sessions; it disrupts the automated workflows, software integrations, and business tools that rely on these APIs for daily operations.
This event serves as a reminder of the systemic risks inherent in the current AI-integrated economy. For many developers, an outage at OpenAI represents a single point of failure that can halt the functionality of entire third-party applications, echoing previous major disruptions seen in cloud computing and infrastructure services.
Why the "Incorrect API key" claim remains unverified
Several critical details regarding the specific cause of the "Incorrect API key" error remain unverified. It is currently unclear whether the error was triggered by a genuine credential synchronization issue or if it was a symptom of a deeper backend failure within OpenAI's authentication layer.
Furthermore, the source does not clarify why the error message specifically targeted API keys when the disruption was also observed on web and mobile interfaces. Until OpenAI provides a detailed post-mortem, users are left to wonder if the issue was a simple configuration error or a more complex failure of the identity management system.
Comments 0