Refresh
Phew – looks like this one is over
Your experience of today’s outage
ChatGPT now seems to be back for many, but according to our poll results, the main problem for most of you was accessing old conversations (with 63% of the vote), compared to 27% who couldn’t log in.
This may reflect what you were doing when the power outage occurred around 10:00 ET / 15:00 GMT, where those already logged in could mostly see issues affecting conversations and image generation, and others were simply locked out at the first hurdle.
Regardless, the chatbot seems to be working okay for most users now, if not all – OpenAI’s latest update at 12:03 ET / 17:03 GMT says it is “continuing to investigate” a “partial outage” affecting ChatGPT and Codex. So if you still have problems, OpenAI continues to work on it…
It returns for many
OpenAI’s status page may still show a “partial outage” for ChatGPT and Codex, but on Downdetector the picture looks a lot rosier – reports are down in both the US and UK.
ChatGPT is working okay 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 poll above or in the comments section below.
OpenAI is still “investigating”.
OpenAI just posted the announcement above on its status page, but unfortunately it’s not a meaningful 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 plus side, the number of reports of Downdetector is dropping quite quickly, so that suggests that the problems are at least abating for many…
A familiar cry
The sentiment above is familiar across X and social media right now – and shows how central ChatGPT has become to our digital lives.
Many still experience a number of problems, from simply getting a blank page on the website to long response times. But for others, like TechRadar’s AI editor, starting a new chat still works fine.
Are you still affected by today’s “partial outage”? Tell us in the poll at the top of this page.
That’s some of the list
This now sounds a bit more serious – OpenAI’s status page has upgraded the incident to “partial outage”, which is colored in red instead of amber.
As you can see above, the list of “affected components” is extensive – ranging from conversations, login, voice mode to image generation. That is why. even if you are logged in (which many are unable to do), you may see error messages for the task you are trying to perform.
OpenAI’s latest update, published at 11.13 ET / 16.13 GMT, is that “we are continuing to investigate the issue for the services listed”.
Not everyone is affected
This is a bit of a curious ChatGPT outage because not everyone is affected in the same way – which is probably why it’s been labeled as “degraded performance” rather than a full outage.
My colleague Graham Barlow, TechRadar’s AI editor, says the web version works for him, but he gets the “unable to load conversation” message above.
Meanwhile, others are having trouble logging in, but some are reporting that Codex is working okay for them – so it looks like this bug could be affecting your ChatGPT usage in a variety of ways.
‘Something seems to have gone wrong’
If you are trying to use the ChatGPT app, you may see this error message right now.
That’s 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.
A rather large tip
Oddly, 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.
This suggests that there may be regional discrepancies, or it may be partially explained by time zone differences.
Regardless, OpenAI says it’s still investigating “degraded performance” across ChatGPT and Codex, and that’s certainly the case for me.
You must verify your public display name before commenting
Please log out and then log back in. You will then be prompted to enter your display name.
Sign out
