From the daily brief · AI
ChatGPT mobile app logins failed for about 3 hours on Oct. 15; OpenAI says it is fixed
If your crew could not sign in to ChatGPT on their phones Thursday morning, that is why. The issue is resolved and the cost to most shops is small.
- What happened
On Oct. 15, 2026, OpenAI's status page reported an issue affecting logins and signups across all ChatGPT mobile apps, first posted at 4:29 PM UTC and soon broadened to "widespread feature degradation." OpenAI applied a mitigation at 5:13 PM and marked the incident resolved at 6:56 PM UTC, listing ChatGPT Login as the one affected component, with a partial outage from 2:30 PM to 5:20 PM.
- What it means for a 10-to-50-person business
The effect is small. The status page lists one affected component: ChatGPT Login. The problem was named in the iOS and Android apps. The API is not listed, and neither is the web version. In US time zones the impact window was a weekday morning: 8:30 to 11:20 AM Mountain. Take a 12-person plumbing shop where 4 techs use the ChatGPT phone app to draft quotes and job notes between calls. If each tech tried to sign in once, failed and fell back to typing notes by hand, that is maybe 20 minutes lost per tech. That works out to about 80 minutes, or roughly $65 at $50 an hour. Techs who were already signed in may not have noticed, though the page does not say. Shops that use ChatGPT only on a desktop, or call OpenAI through other software, can ignore this. The one lasting point: if a field task depends on a single phone app, give people a written fallback.
- What to do
- Ignore
Take no action on this incident; if staff rely on the ChatGPT mobile app for quotes or notes, write a one-line fallback (such as the web version or a notes template) into your field procedures.
- What it costs
What it costs - Lost time, assume 4 techs × 20 min at $50/hr
- ≈ $65 one-off
- New software or plan change
- $0
- Writing a one-line fallback procedure
- 15 min (≈ $13 at $50/hr)
- Doing nothing
- $0; OpenAI marked the incident resolved at 6:56 PM UTC on Oct. 15
- Sources
- status.openai.com (primary)
Questions owners ask
- Did this affect the OpenAI API or tools built on it?
The status page lists only one affected component, ChatGPT Login. The API is not listed among affected components for this incident.
- Should I ask OpenAI for a credit?
The status page says nothing about credits. For a login problem lasting about three hours in the mobile apps, chasing one is unlikely to be worth the time.
Three to five of these, every weekday morning.
Related
Brief · Nov 3, 2026
OpenAI to merge ChatGPT's Chat and Work tabs, with Codex sharing one usage pool
If your staff use ChatGPT and Codex heavily, both now draw on the same allowance, so some users may hit…
Brief · Nov 2, 2026
Zapier now bills AI and code steps in tasks, at rates set by model and runtime
If your Zaps use AI or Code steps, your task count can rise without any change to your plan price, and…
Brief · Nov 2, 2026
Gemini in Google Slides now edits entire decks; promo usage limits run to Dec. 1
If your firm sends client or bid decks every month, Google's new whole deck editing is worth a one hour test…
Brief · Oct 30, 2026
Meta may push new ad and business terms past Nov. 20; current terms stay in place
If you run Facebook or Instagram ads, nothing changes this month: Meta's disputed new terms are on hold, and…