ChatGPT Logins Failed For 53 Minutes. The Next Morning, File Creation Broke.
Three status page incidents since Tuesday night: login and signup on October 1, a Pages outage that ran nearly two days, and errors running code and creating files on October 2. Users say the bugs don't stop at the status page.
A padlock on a laptop keyboard, shown for illustration. Photo: Yuri Samoilov, CC BY 2.0, via Wikimedia Commons.
If ChatGPT kicked you to a login screen that wouldn't let you back in on Thursday, it wasn't your password. OpenAI's own status page logged it, and it was one of three ChatGPT incidents on the page between Tuesday night and Friday morning.
The login outage
At 11:46 AM Pacific on Thursday, October 1, OpenAI posted that it was "investigating an issue affecting login and signup." Twenty minutes later the incident grew to cover "login, signup, and ads." At 12:17 PM the company said it had identified that users were having login issues and was working on a fix. A mitigation went in at 12:26 PM, and the incident was marked fully recovered at 12:39 PM.
That's 53 minutes from the first post to recovery, logged as a major incident. For anyone who was signed out in that window, ChatGPT simply wasn't available.
Pages ran for almost two days
A separate incident, "Elevated errors in ChatGPT Space Pages," opened at 7:20 PM Pacific on Tuesday, September 29. OpenAI said users could see errors creating or using Pages, including failures with Page tools and live Page sessions. Mitigations went in early on September 30, but on the morning of October 1 the company was still warning that some users "may see slow or timed out results, especially for creating new pages or spaces." It wasn't marked resolved until 4:44 PM Pacific on October 1, roughly 45 hours after it started.
Then file creation
On Friday morning, October 2, at 9:03 AM Pacific, a new incident went up: "Some users experienced errors when running code, analyzing data or creating files in ChatGPT." OpenAI said a mitigation was applied and it was monitoring. When we read the page, the incident was still open.
What users are reporting that the status page isn't
On r/ChatGPT the same day, a ChatGPT Work user said every new prompt "works diligently for an hour" and then fails with "Error in Message Stream," after which nothing works until they start a new conversation. They put the cost at 1 hour 20 minutes of their time and 20 percent of their weekly usage, with nothing to show for it.
On r/codex, a user who says they've used Codex for over a year reported that copy and paste stopped working around the time 6.1 Sol came out, including in stable version v160, with errors like "Clipboard is busy" and "Copying already in progress." Their workaround is screenshots and OCR.
Neither of those shows up as an incident. If a long ChatGPT run dies on you, save what you can before you retry, because the usage it burned doesn't come back.
Sources: OpenAI status history, incidents "Issues with login, signup, and ads," "Elevated errors in ChatGPT Space Pages" and "Issues with data analysis and file creation in ChatGPT," read October 2; r/ChatGPT, October 2; r/codex, October 2.