For 53 minutes on 1 October, logging in or signing up to ChatGPT failed for many people. OpenAI's status page attributes this to an issue on its own side, covering login, signup and ads.
Started
18:46 UTC
Duration
Lasted 53m
Source
IsDown
Next time
OpenAI is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: ChatGPT, Login
What happened?
OpenAI's status page opened an incident at 18:46 UTC titled "Issues with login, signup, and ads." The first update said the company was investigating problems affecting login and signup. Twenty minutes later, at 19:06, the scope was widened to explicitly include ads alongside login and signup. At 19:17 OpenAI said it had identified that users were experiencing login issues for the impacted services and that it was working on a mitigation. Nine minutes after that, at 19:26, OpenAI reported that the mitigation had been applied and that it was monitoring recovery. No further update was filed after that point, and the incident's listed duration is 53 minutes, which lines up with the gap between the first and last posted updates. The affected components listed are ChatGPT and Login, which matches the described symptom of people being unable to authenticate. No user reports were filed in this window on this page's own record, so the only account of impact is OpenAI's own four updates. That is a thin record: one company, four timestamped lines, no independent confirmation of what exactly broke on their infrastructure or why login specifically failed. OpenAI's statement does not explain what caused the login failures, only that a mitigation was applied and monitored. No post-mortem has been published for this incident.
Learning
This incident sat in OpenAI's authentication layer, the step where ChatGPT checks who you are before letting you in. That is a different layer to the one most uptime checks watch, because a simple ping or page-load probe against chat.openai.com can come back green even while the login and signup flow underneath is broken, since the page itself still loads. That is why a product built on top of OpenAI's API or ChatGPT can look fine from outside while actual users are stuck at the sign-in screen. Over the last 90 days OpenAI has logged 97 incidents with a median duration of 1 hour 47 minutes, and across all time it averages about 15 incidents a month, so this kind of disruption is routine rather than exceptional for this provider. UptimeRobot's own 30-day figures show 40 incidents detected against OpenAI, 39 resolved, with a median duration of 1h 14m, which gives you a second, independent read on how often and how long these things tend to run. Your own monitoring tells you your product is up. UptimeRobot now watches the provider's half too, so next time something breaks you know which side it was without guessing.
