The ML Model That Worked in March Is Lying to You in June
Model drift doesn’t trigger an alarm. It just quietly costs you money until someone finally checks the math.
Somewhere in your stack right now, a model is making decisions based on a version of the world that no longer exists. It approved a loan, flagged a transaction, priced a policy, or answered a customer using assumptions baked in months ago. Nobody got an error. Nothing crashed. The model is still running exactly as designed. That’s the problem.
This is model drift: the slow, undramatic decay of a machine learning model’s accuracy as the real world stops matching the data it was trained on. It’s not a bug, and patching it isn’t a one-time fix. It’s a structural feature of every statistical model ever deployed, and in 2026, with AI agents and hosted large language models stacked into nearly every workflow, it’s getting harder to see and more expensive to ignore.
Three kinds of drift, one blind spot
Practitioners generally sort model drift into three buckets, and the distinction matters more than most teams treat it. Get this wrong and your monitoring dashboard will glow green while your model quietly gets worse.
| Drift type | What’s actually happening | How you catch it |
|---|---|---|
| Data drift (covariate shift) | The statistical pattern of incoming inputs changes, but the rule mapping input to output still holds | Population Stability Index, Kolmogorov-Smirnov test |
| Concept drift | The relationship between input and output itself changes. The same input now warrants a different answer | Performance tracking on labeled slices, much harder to spot |
| Prediction drift | The model’s output distribution shifts, often a leading signal that something upstream is breaking | Output distribution monitoring |
Concept drift is the one that does the most damage, because input data can look perfectly stable while the underlying logic connecting cause and effect has already broken. That’s the gap our analysis of Zillow’s $500 million iBuying collapse walks through in detail: the inputs looked fine right up until the model’s pricing logic was catastrophically wrong.
The number nobody wants to admit: 91%
Researchers from MIT, Harvard, Cambridge, and the University of Monterrey ran the closest thing the field has to a definitive test. They evaluated 128 model-dataset combinations spanning healthcare, transportation, finance, and weather forecasting, every one of them starting from strong, cross-validated performance. Published in Nature Scientific Reports, the result was blunt: temporal degradation showed up in 91% of cases.
That figure isn’t a vendor survey designed to sell monitoring software. It’s peer-reviewed, and it means drift isn’t an edge case you might encounter. It’s closer to a tax every production model eventually pays.
It also tends to arrive faster than teams expect. Industry research cited by MoldStud puts the figure at 67% of organizations running AI at scale reporting at least one critical, drift-related issue that went unnoticed for over a month. And a separate 2024 survey from Evidently AI found that 32% of production scoring pipelines experience real distributional shifts within their first six months of going live. Drift isn’t a year-three problem. It often starts before the champagne from launch day is gone.
The new villain: your model provider changed it on you
Drift used to be a problem you created yourself, by training on data that aged out. In 2026, most enterprise teams don’t train their own models anymore. They build on top of API providers like OpenAI, Anthropic, and Google, and those providers ship updates to hosted models without asking anyone’s permission first.
That means the model your application was tested against in March may not be the same model answering customer requests in June, even though you changed nothing on your end. Research from FutureAGI, published May 14, 2026, identifies this as a distinct and growing category: silent upstream drift, a failure mode existing monitoring stacks largely aren’t built to catch, because they’re watching your data, not your provider’s weights.
Picture a support agent built on a hosted model. In March, its tone, accuracy, and refusal behavior all check out fine. By June, the provider has pushed an update behind the scenes. Nothing in the company’s own pipeline changed, yet outputs shift, and the company only finds out when customer satisfaction scores drop. If you want to see how this risk compounds across multi-agent systems, our piece on AI agent sprawl and the shadow AI problem covers what happens when drift in one component cascades through an entire agent stack.
The fix isn’t complicated, just neglected: pin your model version instead of pointing at “latest,” and run a canary against a held-out evaluation set whenever the provider ships something new.
What drift actually costs
The clearest dollar figure on record comes from a January 2026 paper on arXiv (2601.08928) evaluating drift detection across more than 30,000 retail demand series from the M5 dataset. The baseline forecast held a 0.048 WMAPE error rate, costing about $10.2 million a year in inventory carrying costs. Left undetected, drift pushed that error to 0.192 WMAPE, an increase of $4.1 million annually. The detection system that caught it cost $9,600 a year to run. That’s a 417x return, and it caught the drift within 4.2 days, 97.8% of the time.
Zoom out and the picture gets less reassuring. A Gartner survey of 782 infrastructure and operations leaders, published April 7, 2026, found that only 28% of AI use cases fully meet their ROI expectations, while 20% fail outright. Drift isn’t the only reason AI projects stall, but it’s a recurring, quantifiable piece of why the promised return doesn’t show up.
“What we can’t solve is what the model is going to tell us about how much capital we need to raise, deploy, and risk.”Rich Barton, Co-Founder & CEO, Zillow Group, via GeekWire
Barton said that explaining why Zillow shut down its Offers home-buying program in November 2021, after a $304 million Q3 write-down and total program losses that outside estimates place between $500 million and $880 million. The company laid off roughly a quarter of its workforce in the process. It remains the most visible case of a model’s drift turning directly into a balance sheet problem, and you can read the full breakdown in our earlier analysis of the Zillow collapse.
How to actually catch it
Detection methodology is where the field has actually matured. Statistical tests give you a number, but the number only matters with the right threshold and the right cadence attached to it.
| Method | What it flags | Practical threshold |
|---|---|---|
| Population Stability Index (PSI) | Shift in input feature distribution | Above 0.25 typically warrants action |
| Kolmogorov-Smirnov (KS) test | Statistical divergence between two distributions | Significant, but check against business impact first |
| Eval-score tracking | Direct performance drop on labeled or held-out data | Alert on drift plus eval drop together, not drift alone |
| Output distribution monitoring | Changes in what the model is predicting, a leading indicator | Useful for catching upstream LLM provider changes |
Evidently AI, an open-source monitoring library with more than 25 million downloads, has become something close to the default starting point for teams building this out.
“We use Evidently to continuously monitor our business-critical ML models at all stages of the lifecycle. It’s become invaluable for flagging drift and data quality issues directly from our CI/CD pipelines.”Customer testimonial featured by Evidently AI, whose tooling is built and maintained under CTO Emeli Dral, instructor for the MLOps Zoomcamp monitoring module
Cadence matters as much as the test you choose. High-velocity systems like fraud scoring and ad ranking need checks every 5 to 15 minutes. Batch models can check at run time. Most enterprises still retrain on a fixed quarterly or biannual schedule, a cadence that research from Arize AI suggests underperforms proactive, trigger-based retraining by roughly 4.2x on prediction stability.
Is drift even the real villain?
Here’s where the consensus narrative gets a useful challenge. A Statsig analysis of the Zillow collapse makes an argument worth sitting with: Opendoor ran a comparable iBuying algorithm in the same overheated housing market and posted a $170 million profit that same quarter. Same conditions, same basic algorithmic approach, wildly different outcomes. If the model itself was the problem, both companies should have failed the same way.
The more uncomfortable read is that drift didn’t sink Zillow on its own. The company’s governance process around model uncertainty did. A model that flags rising uncertainty is only useful if someone with the authority to slow down actually listens to it. “Your model is lying to you” might be less accurate than “your organization has no mechanism for hearing your model admit it’s unsure.”
There’s a second, more technical complication. A 2025 paper accepted at ACM SIGKDD, the field’s top data mining conference, found that the standard fix for concept drift, retraining on recent data, can introduce its own version of the problem. Because ground-truth outcomes arrive after the forecast window closes, there’s “a temporal gap between the training samples and the test sample,” and the researchers found this gap itself can cause forecast models to adapt to outdated concepts, even while they’re being retrained specifically to fix drift.
Worth asking before you greenlight a monitoring budget: is your detection threshold calibrated to business impact, or just statistical significance? A supply chain monitoring study found that KS tests can flag feature shifts that never actually connect to a performance change. Tune your alerts too tight and you get a different failure mode entirely, alert fatigue, where a team that’s been burned by false positives starts ignoring the real signal when it finally shows up.
What to do Monday morning
- Pin your model versions. Stop pointing production traffic at “latest” for any hosted LLM. Run a canary against a held-out eval set before accepting a provider update.
- Set thresholds by business impact, not just statistics. A PSI of 0.3 on one feature might be noise. On another, it’s a five-alarm fire. Know the difference before you wire up alerts.
- Match monitoring cadence to traffic velocity. Fraud and ad ranking systems need checks every 5 to 15 minutes. Slower-moving batch models don’t.
- Alert on drift plus performance drop together. Drift without measurable eval impact is a false alarm that burns your on-call rotation for nothing.
- Build a path from alert to action. Zillow’s failure suggests the weak link often isn’t detection. It’s what happens, organizationally, once the alert fires. If your monitoring talent is already stretched thin, that’s worth examining alongside our look at the enterprise AI skills gap CTOs are now contending with.
None of this requires a massive budget. The DriftGuard research found a monitoring system costing under $10,000 a year preventing millions in losses. The gap between companies that catch drift early and companies that find out from a customer complaint usually isn’t money. It’s whether anyone built the pipe in the first place, a gap our earlier reporting on why most enterprise AI roadmaps stall traces back to the same root cause.
Frequently asked questions
What is model drift in machine learning?
Model drift is the gradual decline in a deployed model’s predictive accuracy as real-world data diverges from the data it was trained on. It happens silently, with no error message, and shows up as either data drift, where input patterns shift, or concept drift, where the relationship between inputs and outputs itself changes.
How do you detect model drift?
Teams compare live production data against the original training baseline using statistical tests. The Population Stability Index, where readings above 0.25 signal real concern, and the Kolmogorov-Smirnov test are the two most common methods. Platforms like Evidently AI, Arize AI, and Amazon SageMaker Model Monitor automate the comparison and fire alerts when thresholds are crossed.
What is the difference between data drift and concept drift?
Data drift means the statistical pattern of incoming inputs changes while the underlying rule connecting inputs to outputs still holds. Concept drift means that rule itself breaks: the same input now deserves a different answer. Concept drift is more dangerous because the input data can look perfectly normal while accuracy quietly collapses.
How often should you retrain a machine learning model?
It depends on how fast your environment moves. Fraud detection and ad ranking systems should be checked every 5 to 15 minutes, with retraining triggered only when drift is confirmed and performance has actually dropped. Batch models can be checked at run time. Most companies still retrain on a fixed quarterly schedule, which research shows is too slow for high-velocity systems.
What causes model drift?
The usual culprits are shifting user behavior, macroeconomic shocks, upstream data pipeline changes, evolving fraud or attack patterns, training-serving skew between lab data and real-world inputs, and, increasingly in 2026, silent updates pushed by the company hosting your large language model.
What percentage of ML models experience drift in production?
A peer-reviewed study from researchers at MIT, Harvard, Cambridge, and the University of Monterrey tested 128 model-dataset combinations across healthcare, transportation, finance, and weather, and found measurable temporal degradation in 91% of them. A separate 2024 industry survey found that 32% of production scoring pipelines drift within their first six months alone.
What tools are used to monitor model drift?
The most widely adopted options in 2026 are Evidently AI, an open-source library with more than 25 million downloads, Arize AI, Fiddler AI, Amazon SageMaker Model Monitor, Microsoft Azure ML Monitor, WhyLabs, and DataRobot MLOps. Teams running large language models are increasingly adding LangSmith and dedicated LLMOps platforms to catch output-level drift.
Is Zillow’s failure an example of model drift?
Yes, with a caveat. Zillow’s Zestimate model, trained on stable historical housing data, failed to adjust as the post-pandemic market cooled, a textbook case of concept drift. But Opendoor ran a comparable algorithm in the same conditions and turned a profit that quarter, which suggests Zillow’s failure to act on model uncertainty mattered as much as the drift itself.
The bottom line
Model drift was never the kind of failure that announces itself. That’s the entire point of the seasonal metaphor: nothing about your model changes the day it starts being wrong. The data underneath it changes first, quietly, and the model just keeps confidently answering questions using a version of reality that expired weeks ago.
What’s different about 2026 isn’t the existence of drift. It’s the speed and the new sources. Hosted LLM providers shipping silent updates, agent stacks where drift in one component cascades into five others, and a Gartner prediction confirming that most organizations still have no dedicated way to see any of it coming. The 91% figure from Nature isn’t a warning anymore. It’s closer to a baseline assumption.
Over the next 6 to 18 months, expect three things to accelerate: AI observability spending climbing toward Gartner’s projected 40% adoption rate, regulatory frameworks in the EU and US increasingly treating documented drift monitoring as a compliance requirement rather than a best practice, and a harder conversation inside companies about whether detection tools matter if nobody acts on what they flag.
Watch your model version pins. Watch your alert thresholds for business relevance, not just statistical significance. And watch what happens, organizationally, the next time a drift alert actually fires.
Stay ahead of the next model failure
Get the data, the case studies, and the contrarian takes other AI newsletters skip, straight from The Neural Loop.
Subscribe to The Neural Loop