LIVE
+++ NVIDIA Pools Home PCs to Run AI Agents Locally +++ OpenAI agents hijacked a German developer wiki +++ Playco says GPT-6 Astra halved its manual game fixes +++ Three AI services went down at once, cause unexplained +++ NBA 2K27 Brings DLSS 5 to GeForce NOW's Cloud RTX 5080s +++ GPT-6 Astra Cuts a 41-Document Review to Minutes ++++++ NVIDIA Pools Home PCs to Run AI Agents Locally +++ OpenAI agents hijacked a German developer wiki +++ Playco says GPT-6 Astra halved its manual game fixes +++ Three AI services went down at once, cause unexplained +++ NBA 2K27 Brings DLSS 5 to GeForce NOW's Cloud RTX 5080s +++ GPT-6 Astra Cuts a 41-Document Review to Minutes +++
All news ›
AI IN LIFE AI IN LIFENEWS
DAILY
DE EN
TOOLS

ChatGPT, Grok and Claude Went Offline Simultaneously

Three rival chatbots stumbled inside the same window on a Thursday. ChatGPT flagged elevated errors near 11AM ET; no cause is confirmed here.

ChatGPT, Grok and Claude Went Offline Simultaneously

Symbolic image: a person works at a server rack while status LEDs blink and cooling fans run in a data center.

ChatGPT, Grok, and Claude all reported trouble within the same stretch of a Thursday and later came back online, with no shared cause established.

At a glance

  • Affected: ChatGPT (OpenAI), Grok (xAI), and Claude (Anthropic) — three chatbots from three competing vendors.
  • The Verge reports ChatGPT began returning errors around 11AM ET, with its status page citing elevated error rates.
  • All three services were reachable again by the time of that report.
  • Not established: the cause, the per-service duration, or whether the outages are technically linked.
  • The one permitted source would not load during production; every detail here comes from the supplied excerpt.

ChatGPT, Grok, and Claude all reported trouble within the same stretch of a Thursday and later came back online, with no shared cause established.

What the report actually says

The account is short. ChatGPT began throwing errors at people trying to use it around 11AM ET, and OpenAI's status page pointed to elevated errors at that moment. Grok, from xAI, and Claude, from Anthropic, ran into problems in the same window. By the time the piece was written, all three were serving requests again.

The gaps we are not filling

No cause is given. No per-service duration is given. Nothing indicates whether the three vendors sit on shared infrastructure — the same cloud region, the same DNS or CDN layer — or how many people were locked out. Closing any of those gaps would take a second newsroom, and this cluster had none.

Simultaneous is not the same as connected

Three chatbots failing in one hour is worth noticing and proves nothing by itself. A common dependency, a mid-morning US traffic peak, and plain coincidence all look identical from the outside. Telling them apart requires incident write-ups from the three companies. We have not seen any.

How this piece was produced

Exactly one independent newsroom covered this story, and its article would not load while we were writing. Everything above is drawn from the supplied excerpt of that article. The house rule of at least two independent sources is therefore unmet, which is stated plainly rather than patched over with links we never opened.

◈ AI-GENERATED REPORT · SOURCES LINKED

FAQ

Were ChatGPT, Grok, and Claude down at the same time?

The report places all three failures in the same Thursday window. Whether they started in the same minute is not something the material specifies.

When did the ChatGPT outage start?

Users hit error messages around 11AM ET, and the status page listed elevated error rates. No end time for the disruption is given.

What caused the outages?

We do not know. Nothing in the material we could review quotes OpenAI, xAI, or Anthropic offering an explanation.