Refresh
Phew, looks like this is over.
Your experience of today’s blackout
ChatGPT now seems to be back for many, but according to our survey results, the main problem for most of you was accessing old conversations (with 63% of the votes), compared to 27% who were unable to log in.
This could reflect what you were doing when the outage occurred around 10am ET / 3pm GMT, with those already logged in mostly seeing issues affecting conversations and image generation, and others simply crashing at the first hurdle.
Either way, the chatbot seems to be working fine for most, if not all, users now: OpenAI’s latest update at 12:03 pm ET / 5:03 pm GMT says it is “continuing to investigate” a “partial outage” affecting ChatGPT and Codex. So if you’re still having problems, OpenAI continues working on it…
It’s coming back for many
OpenAI’s status page may still show a “partial outage” for ChatGPT and Codex, but on Downdetector the picture looks much more optimistic: the number of reports has plummeted in both the US and the UK.
ChatGPT is working fine for me again on the iOS app and web version, so the worst of this outage should be behind us, but if you’re still having issues, let us know in the survey above or in the comments section below.
OpenAI is still “investigating”
OpenAI just posted the above message on their status page, but unfortunately it’s not a significant update.
It says “we are investigating the issue for the listed services” and that “affected users are currently unable to access ChatGPT, Codex, and the API platform.”
On the positive side, the number of reports about Downdetector is decreasing quite rapidly, suggesting that the problems are at least decreasing for many…
A familiar cry
The sentiment above is familiar on X and social media right now, and shows how central ChatGPT has become in our digital lives.
Many are still facing a variety of issues, from simply receiving a blank page on the website to long response times. However, for others, like TechRadar’s AI editor, it still works fine when starting a new chat.
Are you still affected by today’s “partial blackout”? Let us know in the survey at the top of this page.
That’s the whole list
This now sounds a little more serious: OpenAI’s status page has updated the incident to “partial outage,” which is colored red instead of amber.
As you can see above, the list of “affected components” is extensive, from conversations, login, voice mode to image generation. That’s why. Even if you’re logged in (which many aren’t), you may see error messages for the task you’re trying to perform.
The latest update from OpenAI, posted at 11:13 am ET / 4:13 pm GMT, is that “we are continuing to investigate the issue for the listed services.”
Not everyone is affected
This is a slightly curious ChatGPT outage, because not everyone is affected in the same way, which is probably why it was labeled as “degraded performance” rather than a full outage.
My colleague Graham Barlow, AI editor at TechRadar, says the web version works for him, but he gets the “conversation cannot be loaded” message above.
Meanwhile, others are having login issues, but some are reporting that Codex is working fine for them, so it looks like this outage could impact their use of ChatGPT in different ways.
“Something seems to have gone wrong”
If you are trying to use the ChatGPT app, you may be seeing this error message right now.
This is because the chatbot is experiencing “degraded performance” right now, according to OpenAI’s status page.
These affect almost every aspect of ChatGPT, from login to conversations and voice mode. OpenAI says it’s still “investigating,” but that’s all we know so far.
Quite a big beak
Interestingly, the number of reports on Downdetector for these ChatGPT issues is higher in the UK than in the US. It peaked at over 8,000 in the UK, while in the US it is still only 1,875.
That suggests there could be regional discrepancies, or may be partly explained by time zone differences.
Either way, OpenAI says it’s still investigating “degraded performance” in ChatGPT and Codex, and that’s certainly the case for me.
You must confirm your public name before commenting.
Sign out and then sign in again; You will then be asked to enter your display name.
Sign out
