AT&T and GSMA warn Telco AI Models Drift

Boost Mobile data scientist Priyank Jain, GSMA director of AI technologies Louis Powell and AT&T data office vice president Mark Austin flagged a specific and seldom discussed risk in telco AI deployments this week: the gap between the data a model was trained on and the data it actually encounters once it is live, a failure mode known as train serve skew. Speaking to Fierce Network on 25 September 2026, Jain explained that the danger is not a crash or a failed job. Nothing alerts an operator that anything is wrong. Jain said the model "just gets quietly worse."

Two Different Ways Models Drift

The article identifies 2 separate causes. General purpose frontier models arrive with no exposure to telecom specific data formats or vendor taxonomies, since none of that appears in their internet scale training data. Telecom specific models face a subtler problem: production data, such as settlement records, arrives late or out of order in ways the training set never captured, and datasets in this domain routinely carry over 100 columns of custom, operator specific parameters. Powell added that frontier models have no inherent understanding of telecommunications and can produce confident, wrong answers, a real risk once a model is embedded in an enterprise workflow. Austin's prescription is procedural rather than technical: match training data to production sources as closely as possible, run a new model silently alongside the live system before cutting over, and keep testing it after deployment rather than treating the launch as the finish line.

Why This Matters Before Autonomy

This is a narrower and more mundane problem than the industry's current preoccupation with agentic AI and autonomous networks, and that is exactly why it matters. The NGMN report on agentic AI concluded that even coordination within a single operator's own domains, let alone accountability between an enterprise and its network provider, requires common information models and audit trails that do not yet exist. Train serve skew shows the problem starts a level below that. A supervised classifier with a known, static task can still fail silently once its inputs drift from what it was trained on. An autonomous agent negotiating across an operational boundary carries the same drift risk plus the coordination and accountability gap NGMN identified. Operators evaluating agentic AI pilots should ask a more basic question first: whether they would know if the model already in production today has quietly stopped working.

Quiet drifts like this example are worse than explicit failures. The quality of the output degrades silently, which degrades the quality of service. Explicit quality control for data quality before and after transformation, and before and after agentic intervention are necessary to enable autonomous networks.