Industry deploymentGoogle Gemini models (Gemini 2.0 in Vertex AI)Google Cloud Vertex AIGoogle Cloud RunBigQueryFirestoreGoogle Cloud Autonomous Network Operations frameworkA2A (Agent-to-Agent) protocol (intended)Frag Magenta chat and voice bot (generative AI)

Deutsche Telekom put a Gemini-based agent into its live mobile network — major-event response fell from hours to about a minute

Deutsche Telekom AG· Europe (Germany, with rollout to Czech Republic and Croatia); group-wide including United States· Agentic AI for autonomous radio access network (RAN) monitoring, anomaly detection and self-healing remediation, alongside generative-AI customer service automation at group scale
Share
Deutsche Telekom AG logo
Deutsche Telekom AG
Google Gemini models (Gemini 2.0 in Vertex AI) logo
Google Gemini models (Gemini 2.0 in Vertex AI)
AI deployment

Deutsche Telekom's RAN Guardian agent, built with Google Gemini models, went live in Germany in November 2025. Within its first month it autonomously triggered over 100 remediation actions at Christmas market events, and in live operations cut the time needed to manage major events from hours to around a minute. A look at what was actually built, what the numbers do and don't prove, and what the follow-on MINDR system tells us about multi-agent network operations.

Results at a glance · every figure cited

From hours to around a minute — a more than 95% improvementTime to manage major network events (RAN Guardian, live operations)
Over 100 (Christmas market events, from November 2025)Autonomous remediation actions in first month after launch
237,000Events identified by RAN Guardian for 2026
~130 events across 611 mobile sites pre-checked; only 5 sites experienced peak loadsCarnival season coverage
Approximately 2.6 millionFrag Magenta customer service calls handled, H1 2026
Down 55 percent; AI agents handle 40 percent of customer contactsUS customer service calls
30 percent decreaseComplaint reduction in initial proactive-service use cases
More than 100,000Employees trained in using AI
Approximately €2.5 billionTargeted indirect cost savings by 2030 vs 2023 (forward-looking)
Approximately €1.1 billionTargeted gross savings outside the US in 2027 vs 2023 (forward-looking)
Nearly 10 million; more than one-third of requests resolved immediatelyFrag Magenta conversations handled in 2024

The challenge

Mobile networks span multiple domains and technologies, and operational teams rely on fragmented systems that slow root-cause analysis. Deutsche Telekom's own framing is that traditional rule-based automation falls short of real-time 5G demands: when a Christmas market or a Carnival parade draws tens of thousands of people into a few cells, engineers historically needed hours to detect, classify and act on the resulting degradation — by which time customers had already felt it. At the same time the group faced pressure to cut indirect costs and to absorb rising service volumes without proportionally growing headcount.

What was deployed

Deutsche Telekom and Google Cloud built the RAN Guardian agent using Gemini 2.0 in Vertex AI, with Cloud Run, BigQuery and Firestore underneath. The agent continuously analyses network parameters to predict and detect anomalies, classifies and prioritises degradations using monitoring, inventory, performance and coverage data, and then recommends or autonomously implements corrective actions such as resource reallocation and configuration adjustments. It went live in Germany in November 2025 and is now scaling to the Czech Republic and Croatia. The follow-on system, MINDR (Multi-Agentic Intelligent Network Diagnostics & Remediation), extends the same agentic pattern from the RAN alone to RAN, transport and core as a collaborative multi-agent system. On the customer side, the group runs the Frag Magenta chat and voice bot and has given employees AskT, ChatGPT Enterprise and Microsoft Copilot under an 'AI for All' programme.

The results

Deutsche Telekom reports that RAN Guardian reduced the time needed to manage major events from hours to around a minute, a more than 95% improvement, and that it autonomously triggered over 100 remediation actions at Christmas market events in its first month. For 2026 it has identified 237,000 events; during the February Carnival season it pre-checked 611 mobile sites serving around 130 events, of which only 5 experienced peak loads and were adjusted during the event. On the service side, Frag Magenta handled approximately 2.6 million customer service calls in the first half of 2026, US customer service calls have dropped 55% with AI agents handling 40% of contacts, and initial proactive-service use cases show a 30% decrease in complaints. The group targets roughly €1.1bn in gross savings outside the US in 2027 and about €2.5bn in indirect cost savings by 2030, both versus 2023.
TL;DR

Deutsche Telekom built RAN Guardian, an AI agent running on Google Gemini models, and put it into live production in its German mobile network in November 2025. Within its first month it autonomously triggered over 100 remediation actions at Christmas market events, and in live operations reduced the time needed to manage major events from hours to around a minute. A multi-domain successor, MINDR, was announced in February 2026. All figures below come from Deutsche Telekom and Google Cloud; none has been independently audited.

The problem: a network that moves faster than its runbooks

Every mobile operator has the same structural problem. Traffic is not evenly distributed in space or time — it clumps around Christmas markets, Carnival parades, stadiums and festivals — and the operational tooling that detects degradation was built on static thresholds and rules written months earlier. Deutsche Telekom and Google Cloud put the diagnosis bluntly in their original announcement: as telecom networks become increasingly complex, traditional rule-based automation falls short in addressing real-time challenges.

The second, less obvious problem is fragmentation. A modern network spans radio access, transport and core domains, each with its own monitoring stack. When a service degrades, the signal that explains it often sits in a different system from the one that raised the alarm. Deutsche Telekom's later framing of this is that operational teams often rely on fragmented systems that slow root-cause analysis and resolution. Humans bridge those systems by hand, and that bridging is where the hours go.

Traditional network management approaches are no longer sufficient to meet the demands of 5G and beyond. We are pioneering AI agents for networks, working with key partners like Google Cloud to unlock a new level of intelligence and automation in RAN operations as a step towards autonomous, self-healing networks

— Abdu Mudesir, Group CTO, Deutsche Telekom, Deutsche Telekom newsroom, February 2025

What was actually built

RAN Guardian is not a chatbot bolted onto a network operations centre. According to the joint announcement, the agent was built using Gemini 2.0 in Vertex AI, with Cloud Run, BigQuery and Firestore providing execution, analytics and state. The division of labour matters: BigQuery holds the telemetry at scale, Firestore holds agent state, Cloud Run executes, and the model does the reasoning that rules used to do badly.

The published capability set is deliberately narrow. The agent performs autonomous RAN performance monitoring, analysing key network parameters in real time to predict and detect anomalies; AI-driven issue classification and routing, prioritising degradations using network monitoring, inventory, performance and coverage data; and proactive network optimisation, where it recommends or autonomously implements corrective actions, including resource reallocation and configuration adjustments. That is a bounded, largely reversible action space — a design choice worth copying.

How the loop runs

1
Anticipate

The agent identifies upcoming high-impact events and traffic surges — markets, parades, festivals — and the mobile sites that will serve them.

↓
2
Pre-check

Sites serving those events are checked for existing issues before the crowd arrives.

↓
3
Detect and classify

Real-time telemetry is correlated with inventory, performance and coverage data to detect anomalies and prioritise degradations.

↓
4
Act

The agent recommends or autonomously executes corrective actions — resource reallocation, configuration adjustments — during the event.

What the production numbers say

The February 2026 release is where the operational evidence lives, and it is unusually specific for a vendor-adjacent announcement.

~1 minTime to manage major network events, down from hours — a more than 95% improvement in live operationsSource: Deutsche Telekom, 2026
100+Remediation actions triggered autonomously at Christmas market events in the agent's first monthSource: Deutsche Telekom, 2026
237,000Events identified by RAN Guardian for 2026Source: Deutsche Telekom, 2026
611Mobile sites pre-checked for Carnival events; only 5 hit peak loads and were adjusted liveSource: Deutsche Telekom, 2026

The Carnival example is the most instructive. Deutsche Telekom reports that during the February Carnival season the agent identified around 130 events and parades each expected to draw over 10,000 participants, served by 611 different mobile sites, all pre-checked for issues by RAN Guardian, with most also monitored live. Five sites actually hit peak loads and were adjusted during the event. That ratio — hundreds of sites watched, a handful touched — is what a well-tuned agent looks like. An agent that intervened on 200 of 611 sites would be a liability, not an asset.

From one domain to many: MINDR

Having proved the pattern in the radio access network, Deutsche Telekom generalised it. MINDR — Multi-Agentic Intelligent Network Diagnostics & Remediation — applies the same agentic principles at the service level across RAN, transport and core. It was developed with Google Cloud's Autonomous Network Operations framework, and built with Google Gemini models on Vertex AI, operating as a collaborative multi-agent system in which specialised agents collect and correlate network data, build a real-time end-to-end view of service performance, and support root-cause analysis and controlled remediation across domains. The company also stated an intention to use the A2A (Agent-to-Agent) protocol for coordination, subject to its availability.

MINDR extends AI-driven intelligence from individual network domains to an end-to-end service approach, enabling us to proactively diagnose and resolve issues before any customer impact. It represents another significant step toward autonomous, self-healing networks.

— Abdu Mudesir, Board Member, Product & Technology, Deutsche Telekom, Deutsche Telekom newsroom, February 2026

Note the sequencing, because it is the part most organisations get wrong: single agent, single domain, single country, in production for a quarter — then multi-agent, multi-domain, multi-country. Following the German rollout, RAN Guardian is scaling across Deutsche Telekom's European national companies, starting with the Czech Republic and Croatia.

The other half: service automation at group scale

The network agent is the sharpest story, but it sits inside a much broader programme that Deutsche Telekom laid out at its AI Investor Day in Bonn on 5 October 2026. On the customer-facing side, the company reported that the chatbot Frag Magenta handled approximately 2.6 million customer service calls in the first half of 2026 alone, that in the US the number of customer service calls has dropped by 55 percent with AI agents there handling 40 percent of customer contacts, and that initial proactive-service use cases show a 30 percent decrease in complaints.

Frag Magenta itself long predates the generative-AI wave. Deutsche Telekom's own description notes it now helps with more than 380 different requests, can access individual customer data after login to perform tasks such as retrieving bills or changing bank details, and that in 2024, "Frag Magenta" handled nearly 10 million customer conversations. The chatbot resolves more than one-third of requests immediately. When it fails, it hands the human agent the transcript and a summary — a deflection design that treats escalation as a first-class path rather than a failure state.

SystemDomainAutonomyPublished evidence
RAN GuardianRadio access networkAutonomous remediation within a bounded action spaceHours to ~1 minute; 100+ autonomous actions in month one; 237,000 events identified for 2026
MINDRRAN, transport and coreMulti-agent, explainable, controlled remediationDesigned, tested and verified; first production releases planned for later in 2026
Frag MagentaCustomer service (chat and voice)Resolve-or-hand-off, with human escalation~2.6m service calls in H1 2026; ~10m conversations in 2024; >1/3 resolved immediately
AskT / Copilot / ChatGPT EnterpriseEmployee productivityHuman-in-the-loop by designMore than 100,000 employees trained in using AI

The money — and where the evidence thins out

At the investor day the group set out targets rather than realised results: for 2027, Telekom expects AI and automation to generate gross savings of approximately 1.1 billion euros outside the U.S. compared to 2023 . By 2030, it aims to achieve savings of approximately 2.5 billion euros in indirect costs, also compared to 2023. On the revenue side, it expects roughly €250 million in AI-related revenue from businesses outside the US in 2026, rising to about €800 million by 2030.

What matters most is that technology delivers measurable value, for our customers and for our company.

— Tim Höttges, CEO, Deutsche Telekom, Deutsche Telekom newsroom, October 2026

Those are the right words. They are also, in the public record, applied unevenly. The network numbers are specific and dated. The savings numbers are multi-year targets carried in a release that explicitly flags its own forward-looking statements as subject to risks and uncertainties largely outside the company's control. Treat the first as evidence and the second as guidance.

!

Reading a group savings target as a per-use-case ROI

A €2.5bn indirect-cost target spans network operations, customer service, software development and administration, across dozens of entities and seven years. It cannot be decomposed into a payback period for any individual agent, and Deutsche Telekom has not published the compute, licensing or engineering cost of RAN Guardian or MINDR. Business cases built by scaling someone else's headline savings to your own revenue are fiction.

Fix: borrow the measurement design, not the number. Pick one process with a machine-readable before/after — time-to-detect, time-to-resolve, actions per event — and instrument it before the agent ships. See how we approach this in automation and case studies.

What the public record does not establish

Four gaps are worth naming plainly. First, precision: the company reports over 100 autonomous remediation actions in month one, but not how many were later judged correct, nor the false-positive rate. Second, guardrails: the releases describe explainable remediation and controlled action, but not the approval thresholds, rollback mechanism or human-override design that sit behind an agent allowed to change live network configuration. Third, customer outcome: no CSAT, churn or complaint metric is attributed specifically to RAN Guardian — the 30% complaint reduction cited at the investor day relates to proactive service use cases in the connection-provisioning context, not to the RAN agent. Fourth, status: MINDR was described in February 2026 as having first production releases planned for later that year, and we found no subsequent Deutsche Telekom release confirming it reached production.

There is also an attribution question on the service side. The 55% drop in US customer service calls appears in the same paragraph as AI deployment, but the release does not isolate how much of that decline is AI-driven versus the product, app and process changes T-Mobile US has made in parallel. An honest reading is: directionally strong, causally unproven.

What an integration team should take from this

The transferable lesson is scope discipline. Deutsche Telekom did not start by asking a model to run the network. It picked one domain with dense, machine-readable telemetry; one recurring event class with a predictable shape (crowds generate traffic surges at known times and places); one bounded set of actions the agent was permitted to take; and one metric with a clean before/after. That is why a number like "hours to around a minute" is quotable at all — the baseline existed and was measured.

The second lesson is architectural sequencing. Pre-check, detect, classify, act is a pipeline, not a prompt. Most of the value in the Carnival example comes from the first step: anticipating which 611 sites matter before anything degrades. Teams evaluating model options often over-index on reasoning quality and under-invest in the retrieval and correlation layer that decides what the model even sees — here, BigQuery telemetry joined to inventory, performance and coverage data.

The third is that multi-agent is an upgrade path, not a starting point. MINDR's A2A coordination and cross-domain correlation only became tractable once a single-domain agent had earned operational trust. If you are considering a similar progression in your own operations, our research and services pages cover how we evaluate readiness — or you can get started with a scoped assessment.

Feb 2025

Deutsche Telekom and Google Cloud announce the RAN Guardian agent, built with Gemini 2.0 in Vertex AI, and demonstrate it at Mobile World Congress.

Nov 2025

RAN Guardian goes live in production in Germany; over 100 remediation actions triggered autonomously at Christmas market events in its first month.

Feb 2026

MINDR announced as a multi-agent, multi-domain successor; RAN Guardian begins scaling to the Czech Republic and Croatia.

Oct 2026

At its AI Investor Day in Bonn, Deutsche Telekom targets ~€2.5bn in indirect cost savings by 2030 versus 2023 and ~€800m in AI-related revenue outside the US by 2030.

We’re just getting started. We want to roll out across the entire company what’s working today in individual applications. This will enable us to grow faster, work more efficiently, and set new standards for quality.

— Tim Höttges, CEO, Deutsche Telekom, Deutsche Telekom newsroom, October 2026

Frequently Asked Questions

What is Deutsche Telekom's RAN Guardian agent?

RAN Guardian is an AI agent that monitors Deutsche Telekom's radio access network, detects anomalies and executes corrective actions. It was built with Google Cloud using Gemini 2.0 in Vertex AI, with Cloud Run, BigQuery and Firestore supporting it. It analyses network parameters in real time, classifies degradations using monitoring, inventory, performance and coverage data, and either recommends or autonomously implements fixes such as resource reallocation and configuration adjustments.

What measurable results has Deutsche Telekom reported?

In live operations the agent reduced the time needed to manage major events from hours to around a minute, which the company describes as a more than 95% improvement. In its first month after launching in November 2025 it autonomously triggered over 100 remediation actions at Christmas market events. For 2026 it identified 237,000 events, and during Carnival it pre-checked 611 mobile sites, of which only five required live adjustment.

How is MINDR different from RAN Guardian?

RAN Guardian operates within the radio access network only. MINDR applies the same agentic principles at the service level across RAN, transport and core domains, using specialised agents that correlate signals end-to-end and support explainable remediation. It was built with Google Gemini models on Vertex AI using Google Cloud's Autonomous Network Operations framework, and intends to use the A2A protocol for agent coordination.

Are the €2.5 billion savings already achieved?

No. The figure is a target presented at Deutsche Telekom's AI Investor Day in October 2026: approximately €2.5 billion in indirect cost savings by 2030 compared with 2023, with roughly €1.1 billion in gross savings outside the US expected in 2027. The release carries a forward-looking-statements disclaimer. These are group-wide targets spanning network, service, software and administration, not realised per-system results.

What has Deutsche Telekom not disclosed?

The company has not published false-positive rates for the agent, how many autonomous actions were later judged correct, the guardrail and rollback design behind autonomous network changes, or the compute and engineering cost of the systems. No customer-experience metric is attributed directly to RAN Guardian, and no independent third party has audited the figures. MINDR's production status after February 2026 is also not confirmed in any later release we located.

Twarx analysis

Original interpretation

The most credible agentic-AI result in this programme is not the billion-euro savings headline — it is a narrow, well-instrumented loop: one network domain, one recurring event class (crowd-driven traffic surges), a measurable before/after (hours to about a minute), and a bounded action space (resource reallocation and configuration adjustments). Deutsche Telekom proved the pattern in the RAN first, then generalised it to transport and core with MINDR. Scope discipline, not model choice, is what made the number auditable.

Three things an integration team should take from this deployment. First, pick a domain where the ground truth is machine-readable. RAN telemetry gives an agent continuous, high-frequency signals and an unambiguous success criterion, which is why Deutsche Telekom could quote a time-to-manage delta rather than a satisfaction survey. Second, constrain the action space before you grant autonomy. The published description of RAN Guardian limits the agent to resource reallocation and configuration adjustments — reversible, bounded operations — and the MINDR design explicitly emphasises explainable remediation. Third, sequence single-agent before multi-agent. RAN Guardian ran in one domain in one country for roughly a quarter before the multi-agent, multi-domain MINDR architecture was announced, and before the agent was replicated into the Czech Republic and Croatia. Teams that start with a mesh of agents across every domain have no clean baseline and no way to attribute an outcome. The weaker part of the public record is the economics: the group reports group-level savings targets, not per-agent unit economics, which is the normal pattern in investor communications and the normal gap for anyone trying to build a business case from someone else's press release.

Read the numbers honestly

Every figure here comes from Deutsche Telekom or its partner Google Cloud; none has been independently audited or verified by a third party. The €1.1bn and €2.5bn savings numbers are forward-looking targets presented at an investor day, not realised results, and the release itself carries a forward-looking-statements disclaimer. Deutsche Telekom has not published the compute, licensing or engineering cost of these systems, so no net ROI can be computed from the public record. For RAN Guardian specifically, the company has not disclosed false-positive rates, how many of the 100+ autonomous remediation actions were subsequently judged correct, what guardrails or rollback mechanisms constrain autonomous changes, or any customer-experience metric (CSAT, NPS, churn) directly attributed to the agent. The 'more than 95% improvement' is a time-to-manage comparison against an unspecified baseline process. The 55% drop in US customer service calls is not attributed solely to AI in the source text, and no AI system is named for it. MINDR was described in February 2026 as designed, tested and verified with first production releases planned for later that year; we found no subsequent Deutsche Telekom release confirming MINDR is in production. Headcount effects of these specific systems are not broken out.
agentic AItelecommunicationsnetwork operationsGoogle GeminiVertex AImulti-agent systemsAI customer serviceDeutsche Telekomautonomous networksenterprise AI case study
RS

Analysis by

Rushil Shah · AI Systems Builder & Founder, Twarx

Agentic AIMulti-Agent SystemsAI Workflow Automationn8nLangGraphAI Integration

From evidence to deployment

Want telecommunications results you can measure — and defend?

We deploy and audit AI agents the way we research them: real baselines, cited outcomes, and no inflated ROI. Twarx maps where an agent actually pays off for your team — and, just as honestly, where it won't.

  • A utility audit before you build — so budget goes where it moves the metric
  • Source-grounded benchmarks, not vendor marketing numbers
  • Deployed with measurement baked in, so ROI is provable later
Book a utility audit

The teams that win with AI agents aren't the ones with the boldest claims — they're the ones who measured honestly and deployed where the evidence actually pointed.

— Twarx Research