OpenAI's ChatGPT Recovers From Major Afternoon Outage – Dataconomy

Welcome to the forefront of conversational AI as we explore the fascinating world of AI chatbots in our dedicated blog series. Discover the latest advancements, applications, and strategies that propel the evolution of chatbot technology. From enhancing customer interactions to streamlining business processes, these articles delve into the innovative ways artificial intelligence is shaping the landscape of automated conversational agents. Whether you’re a business owner, developer, or simply intrigued by the future of interactive technology, join us on this journey to unravel the transformative power and endless possibilities of AI chatbots.
OpenAI’s ChatGPT experienced a partial outage this afternoon, disrupting access for many users worldwide. Down Detector recorded more than 12,000 reports at the peak. OpenAI reported elevated error rates for ChatGPT and Platform users, marking resolution at 5:14 PM ET.
Users encountered difficulties accessing the AI chatbot during the disruption. Down Detector, a service tracking user-submitted outage reports, logged the surge in complaints around the peak of the issue. OpenAI issued a status update shortly after the problems emerged, specifying “elevated error rates” impacting both ChatGPT directly and its associated Platform services.
The company designated the main outage as resolved at precisely 5:14 PM ET. An active status alert remains in place solely for the fine-tuning component within OpenAI’s API service. Regarding this lingering matter, OpenAI provided the statement: “We have applied the mitigation and are monitoring the recovering.”
Don’t miss out on the latest insights, trends, and analysis in the world of data, technology, and startups. Subscribe to our newsletter and get exclusive content delivered straight to your inbox.
Anthropic’s Claude AI chatbot faced a comparable outage on the same day. Its status page listed “Elevated error rate on API across all Claude models.” Anthropic addressed and resolved this disruption by 1 PM ET.
Featured image credit

source

Scroll to Top