AI services · Daily incidents
AI incidents: ChatGPT login recovery, Codex mitigation and cost-data delays — 16 October 2026
OpenAI resolves ChatGPT mobile login disruption, reports Codex capacity mitigation and monitors delayed cost data. Official timelines, scope and remaining uncertainty.
Publisher disclosure: MUVO offers competing music, remix, and video tools. This report summarizes public sources and provider documentation; it is not an independent product test or a claim that MUVO is free of similar issues. Read our reporting method.
Incident summary and status at the cutoff
ChatGPT mobile access has recovered according to OpenAI; two separate follow-ups concern Codex interruptions and delayed cost reporting. These findings concern different workflows and do not establish one company-wide outage.
This edition covers 13 October at 12:14 through 16 October at 12:00 Europe/Istanbul (UTC+3). Earlier accounts are included only to explain material follow-ups. It does not cover the rest of 16 October.
| Affected workflow | Latest supported status | Source event, Istanbul time |
|---|---|---|
| ChatGPT iOS/Android login and signup | Provider-reported recovery | 15 October, 21:56 |
| Codex capacity interruptions | Support reports mitigation; individual recovery unverified | 15 October, 21:52 |
| Compliance API cost data | Fix deployed; backlog still delaying data | 16 October, 01:36 |
ChatGPT mobile: login and signup disruption resolved
OpenAI marked its ChatGPT feature-degradation incident resolved on 15 October. Its first notice specifically named login and signup across ChatGPT mobile apps; a later notice described wider feature degradation including iOS/Android access. The listed component is ChatGPT Login. Original incident and updates.
The provider’s public timeline, all on 15 October in Istanbul time, is:
- 19:29: First acknowledgement of mobile login/signup trouble.
- 19:35: Expanded description of affected features.
- 20:13: Mitigation applied; recovery being monitored.
- 21:56: Provider reports recovery of impacted services.
These are notice times. The source does not establish the actual impact start, cause, affected regions or a separate customer-recovery timestamp, so we do not calculate an outage duration. It supplies no specific workaround. Recovery does not prove that every account or previously interrupted action completed successfully, and the notice does not establish an API or Sora outage.
Codex: support reports added capacity to reduce interruptions
An OpenAI Support reply on 15 October at 21:52 Istanbul says capacity was added and changes shipped to reduce interruptions. The reply appears in the previously covered capacity-error discussion and asks affected users to try their session again, reporting the error time and timezone if it still stops. Dated provider reply.
This is a material response to the 11 October customer reports, not a newly established outage. Neither an exact mitigation time nor universal recovery is confirmed. The separate feedback-permissions problem is still directed to private support. Keep private logs and conversation contents out of public replies.
OpenAI cost reporting: fix deployed, delayed data still catching up
OpenAI moved its cost-data incident to monitoring at 01:36 Istanbul on 16 October. The provider says a fix is deployed, while Compliance API cost data remains delayed during backlog processing. Earlier updates explicitly excluded API and ChatGPT usage from the impact. Official reporting incident.
This continues the 14–15 October reporting delay, rather than a new generation failure. Normal data freshness and a final resolution time are not yet confirmed. Users of cost reports can consult the alternative reporting channels identified by OpenAI and follow the notice for backlog completion; the evidence does not establish incorrect charges.
Sources
- OpenAI status: ChatGPT mobile access and feature degradation, acknowledged and resolved 15 October.
- OpenAI Support: capacity-mitigation reply, 15 October, 18:52 UTC / 21:52 Istanbul.
- OpenAI status: delayed Compliance API cost data, latest update 15 October, 22:36 UTC / 16 October, 01:36 Istanbul.
We also checked Anthropic, Google, ElevenLabs and specialist music, video and remix/stem sources. Previously covered recoveries were deduplicated. New isolated complaints did not meet the publication threshold. Google’s dedicated Gemini status source and several other histories were inaccessible or incomplete; those gaps are not evidence of normal service. We have not reproduced private customer issues or measured prevalence. See our reporting method.
Launches and releases appear separately in the 16 October AI news edition.
Update timeline
- 16 October 2026, 12:00 Istanbul: Research cutoff. Added the resolved ChatGPT event and two material provider follow-ups. The 11 and 15 October editions receive dated notes while retaining their original publication dates and cutoffs.