Unlike the recent mobile device network outage recently, where affected users were screaming fowl within minutes, AI experienced an outage today and you probably didn’t even know about it. AI Outage with three systems down simultaneously.
Following a prolonged outage in the early morning hours, OpenAI’s ChatGPT chatbot experienced another disruption, but this time, it wasn’t alone. On Tuesday morning, both Anthropic’s Claude and Perplexity also encountered issues, albeit these were swiftly resolved compared to ChatGPT’s downtime.
ChatGPT had seemingly recovered from what OpenAI described as a “major outage” earlier today, which hit millions of users worldwide. As of 3PM ET, the generative AI platform reported “All Systems Operational.”
Reports indicate that Google’s Gemini was operational, although there were some user claims suggesting it might have briefly experienced downtime as well.
The simultaneous outage of three major AI providers is uncommon and could suggest a broader infrastructure issue or a problem at an internet-scale level, akin to the outages affecting multiple social media platforms concurrently. Alternatively, the issues faced by Claude and Perplexity might have been a result of an overwhelming surge in traffic following ChatGPT’s outage, rather than inherent bugs or technical glitches.
What has happened to all the AI platforms? An unknown glitch has affected the activity of most of the chatbots based on generative artificial intelligence (GenAI) on Tuesday, led by OpenAI’s ChatGPT and Google’s Gemini.
What has happened to all the AI platforms? An unknown glitch has affected the activity of most of the chatbots based on generative artificial intelligence (GenAI) on Tuesday, led by OpenAI’s ChatGPT and Google’s Gemini.
Although they have not yet reached the status of critical services such as a search engine, email or an instant messaging application, the scope of use of AI platforms is on a steady rise, for private use, work or studies.
During ChatGPT’s outage, users were unable to message the AI chatbot from its landing page. The disruption began at approximately 7:33 AM PT and was resolved around 10:17 AM PT, marking another instance of multi-hour downtime.