# OpenAI Resolves ChatGPT Login and Signup Disruption > Source: > Published: 2026-08-20 00:28:11+00:00 # OpenAI Resolves ChatGPT Login and Signup Disruption OpenAI resolved a ChatGPT disruption early August 20 after a status incident said chatgpt.com signups and logins were down. The company identified login errors at 12:03 a.m. and marked affected ChatGPT service recovered at 12:54 a.m., ending an interruption that prevented some users from authenticating or creating accounts. OpenAI resolved a ChatGPT service interruption early August 20 after users encountered problems signing in and creating new accounts. On its public status page, the company described chatgpt.com as down for signups and logins and later marked the affected ChatGPT service as recovered. The incident timeline records elevated errors at 12:02 a.m. and says OpenAI had identified login issues by 12:03 a.m. The company reported that it had applied a mitigation and was monitoring recovery before declaring the incident resolved at 12:54 a.m. The status entry does not give a root cause or identify a specific subset of users beyond the affected ChatGPT component. 9to5Mac separately reported that users were seeing account-login and account-creation errors, matching the scope described in the status incident. The report is useful corroboration of the user-facing effect, while OpenAI's status page is the primary record for the interruption and its resolution. ### What the disruption affected Authentication failures can block more than an active chat session. Users who are signed out may be unable to return to saved work, and prospective users cannot complete account creation until the service recovers. For teams that rely on a hosted assistant in daily workflows, this is a reminder to distinguish application availability from model quality: an otherwise functioning model is not reachable when the account and session layer fails. OpenAI's incident record shows that recovery was confirmed within the same early-morning window. It does not establish that every individual login problem during that period shared the same cause, nor does it announce a product change. The useful operational signal is narrower: login and signup access was disrupted, mitigation was applied, and the company subsequently marked the service recovered. ## Key Points - 1OpenAI's status page recorded ChatGPT signup and login failures, then marked the affected service recovered on August 20. - 2The incident timeline listed elevated errors at 12:02 a.m., identified login issues at 12:03 a.m., and a resolved status at 12:54 a.m. - 3The public record describes the access disruption and recovery but does not state a root cause. ## Scoring Rationale This was a short, resolved access incident rather than a product release, but it directly affected ChatGPT authentication and account creation. It is useful operational context for teams that depend on the service, while its limited duration and lack of disclosed root cause keep the impact moderate. ## Sources Primary source and supporting public references used for this report. Practice interview problems based on real data 1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with. [Try 250 free problems](/problems)