ChatGPT logins broke on every mobile app, and OpenAI's incident ran two hours and 26 minutes
Logins and signups stopped working across every ChatGPT mobile app on October 15, and OpenAI rated the failure major. The record on OpenAI's own incident feed opens at 16:29:26 UTC and closes at 18:56:00 UTC, two hours, 26 minutes and 34 seconds later, as the feed stood when it was read at 02:53 UTC on October 16.
OpenAI's DevDay 2026 recap artwork. Image: OpenAI
The first update named the surface and nothing else. "We are investigating an issue affecting logins and signups across all ChatGPT mobile applications," OpenAI wrote at 16:29:26 UTC. "We will provide updates as we learn more."
The scope widened six minutes in
At 16:35:24 UTC the description grew. OpenAI said it was "investigating widespread feature degradation, including issues affecting logins and signups in the ChatGPT iOS/Android apps", and "Widespread feature degradation" is the name the incident carries. OpenAI never said what else degraded.
A mitigation went in at 17:13:05 UTC, 43 minutes and 39 seconds after the first update: "We have applied the mitigation and are monitoring the recovery." The close came one hour and 43 minutes after that, at 18:56:00 UTC.
OpenAI logged no components and no cause
The entry carries no component list, no cause, no user numbers, no regions and no app versions. OpenAI never marked it identified either, the status it uses once it knows what has gone wrong: this one went from investigating straight to monitoring. That is a thinner record than the September 29 outage OpenAI broke down across 30 components, and thinner than its October 9 Android incident, where it at least published a workaround.
The major rating is OpenAI's own and it is not handed out often. Of the 25 incidents the feed was carrying, back to October 2, four are rated major: this one, the two on October 9, and the desktop build that could not open new ChatGPT Work threads on October 7.
What the two updates do establish is where the fault sat. Logins and signups are the way into the app rather than a feature inside it, so for most of that window a phone with no session on it had nothing to open, and a new account could not be made at all. OpenAI says nothing about accounts that were already signed in.
Costs data in the Compliance API has slipped twice in six days
A separate and much smaller problem sat alongside it. OpenAI opened a minor incident at 17:00:44 UTC on October 14 over delayed organisation cost data in the Compliance API, said in its first three updates that "API and ChatGPT usage are not affected", and at 22:36:42 UTC on October 15 said it had "deployed a fix" with the backlog still processing. That one was still open when the feed was read.
An identical delay ran from 17:23:18 UTC on October 9 to 16:02:47 UTC on October 12, 70 hours and 39 minutes. It is an administrator's reporting problem rather than anything a ChatGPT user would see.
Anyone locked out of the app on October 15 has no version number to blame and no advice to follow. What OpenAI left behind is a clock, a label and the sentence it closed with: "All impacted services have now fully recovered."
Note: Links to online stores in articles can be so-called affiliate links. If you buy through this link, MIXED receives a commission from the provider. For you the price does not change.