Grok Started Answering Some Users With Total Gibberish

[Always_Shane35]

An unusual glitch caused xAI's Grok chatbot to respond to some users with strings of nonsensical, unrelated words rather than coherent answers. One affected user asked Grok to generate a PDF and instead received several paragraphs beginning with something like match it without and your they and two for planets can practical, continuing in similarly meaningless fashion for multiple paragraphs straight.

Another user reported that when they checked the source links Grok had cited alongside its garbled response, the links pointed to a string of reinforcement learning research websites, which is a genuinely odd detail suggesting whatever went wrong may be tied to the model's underlying training or fine tuning process rather than a simple frontend display bug. Affected users told reporters the issue seemed to specifically hit Grok Lite and had been happening since at least Wednesday morning.

What makes this notable beyond just being a funny glitch is the disconnect between what users experienced and what xAI's own status page reported. The company's official status tracker showed all Grok services fully operational with no incidents throughout the entire episode, even as multiple users were independently reporting the exact same word salad problem across different accounts and different requests.

TechCrunch reported it was unable to reproduce the issue in its own testing, which suggests this is likely affecting a fairly narrow subset of users or specific query types rather than the entire platform at once. xAI did not respond to a request for comment on what caused the glitch or how many people were actually affected.

Model glitches like this are a useful reminder that even a well funded frontier lab's production systems can quietly misfire in ways that are genuinely hard to reproduce, diagnose, or even publicly acknowledge in real time

Grok keeps sending gibberish responses to users | TechCrunchtechcrunch.com

[IronFist56]

xAI simply not responding to a request for comment feels like the standard playbook at this point whenever something embarrassing happens that a company genuinely cannot yet explain internally. Silence buys time to actually investigate quietly, but it does very little for user trust in the moment itself

[Brooke_19]

Watched a similar failure mode happen with a completely different AI product a while back and it genuinely traced back to a corrupted checkpoint that somehow slipped through an automated deployment pipeline without anyone catching it in review. Would not be shocked if something structurally similar turns out to be the actual root cause here too