Context rot occurs when enterprise AI systems accumulate too much data in LLM context windows, causing conflicting information, hallucinations, and degraded reasoning. As new data is added without removing outdated content, models exhaust their attention budgets and lose accuracy. Elastic's Abhimanyu Anand explains that symptoms include agents looping endlessly, increased latency, and wrong answers. Fixes involve monitoring token consumption and response times, using semantic search tools like Elastic's ELSER, vector stores, and observability platforms to retrieve only the most relevant context. Analyst James Kobielus emphasizes that strong LLMOps governance—including purging stale data before it enters RAG workflows—is essential to prevent a vicious cycle of model drift and diminishing validity.
Table of contents
What is “context rot?”How the problem of context rot surfaces when enterprises use AIHow to fix context rotContext rot requires enterprises to constantly fight back: AnalystSort: