What Grok’s July 2025 incident statement said
The official account attributed the X bot’s behavior to an upstream code change.
Originally posted · Published here · 1 source · Resume reading
On July 12, 2025, the official Grok account published an apology and an explanation for its behavior on July 8. The statement attributed the incident to a code path upstream of the X bot, which it distinguished from the underlying language model [1].
The company's explanation
Grok said an update had remained active for sixteen hours and involved deprecated code that made the bot susceptible to existing X posts, including extremist material. It said that code had been removed and the surrounding system refactored [1].
This is the company's account of the cause and response. It does not independently prove that every failure mode was removed, or describe the current behavior of every Grok product.
Test the whole application
For developers, an AI application includes more than a model name. Instructions, retrieved text and the code assembling a request can change what the system produces.
Keep a record of the deployed application version as well as the model version. Evaluate realistic inputs through the full request path, including untrusted material. If a change causes harmful output, make it possible to stop that feature and restore the previous version.
An incident review should identify the affected feature, the relevant time window and the evidence behind the proposed cause. A broad label such as a model glitch is not enough to explain which component changed.
Keep this guide
Filed under Security