Germany’s Entire Rail Network Went Dark Last Night. Here’s What Happened.

Update: A Software Update may have caused the failure of the GSM-R network in the entirety of the Deutsche Bahn. According to available information, the issue was caused by a contractor – not Deutsche Bahn – after a hardware component was replaced, which unexpectedly triggered a software fault. Standard practice would normally involve testing the change in a limited environment before deploying it across the production system, but that step appears to have been skipped. The work was also performed on the primary system instead of the redundant backup. Because engineers initially could not determine whether the secondary system had also been affected, they were unable to switch over immediately, extending the disruption.

Following the incident, the maintenance process was revised. Similar work will now be scheduled during overnight maintenance windows (roughly midnight to 4 a.m.) and carried out on the backup system first, reducing the impact if a failure occurs before changes are applied to the primary system.

There have also been unverified reports that the contractor took disciplinary action against some employees after the incident. However, these claims are based on indirect accounts and should be treated as unconfirmed.

Original Article Continues Below

Late Tuesday, Germany’s national rail network stopped. Not delayed. Not partially disrupted. Completely Stopped. Every Deutsche Bahn train across the country stopped abruptly wherever it was, going nowhere.

The culprit? a failure in GSM-R, the Global System for Mobile Communications for Railways. It’s the backbone of how train drivers talk to traffic control centers. When it goes down, trains don’t move. Not because there’s a safety threat in the conventional sense, but because no communication means no authorization to move, and rail safety protocols are unambiguous about that. You sit and wait.

Deutsche Bahn confirmed the outage around midnight. “All trains are currently being held at stations,” the company said. “Our technicians are working flat out to resolve the issue.” They’d identified the cause, they added, without saying what it was. That last part matters, and I’ll come back to it.

Two and a Half Hours of Silence

The outage ran for roughly two and a half hours before Deutsche Bahn announced it was fixed, just before 1 a.m. Wednesday. “Our IT experts worked tirelessly to resolve the issue successfully,” the company said, which is exactly the kind of sentence you write when you don’t want to say anything substantive. Services began returning gradually. Some disruption continued into Wednesday morning.

At Munich’s main station, departure boards were telling passengers not to board. Travellers with luggage stood on platforms or queued at information counters. One American passenger, described trying to get back to Munich from Berlin. “The train conductor was very nice, but he was just like, we don’t know,” she said. “She said that we booked a bus for 8 a.m. just in case, but in general, we don’t know what’s going on.”

Deutsche Bahn CEO Evelyn Palla was quoted by Bild saying they stabilized the situation using an emergency system. The company issued taxi and hotel vouchers, kept some trains at stations so passengers had shelter, and apologized.

What they didn’t do is explain what failed or why.

Why GSM-R Matters

GSM-R has been Europe’s standard railway communications protocol since around 2000, when the EU Agency for Railways rolled it out as a shared operations framework. It handles voice and data between drivers and control centers, train-to-ground signaling, and operational coordination across the entire network.

This is infrastructure that looks invisible until it isn’t. The entire German rail network, every S-Bahn, RE, RB, and ICE line, runs on this shared communication backbone. A single nationwide outage can take it all down simultaneously, which is exactly what happened Tuesday night.

That’s not a small design problem. It’s a systemic concentration risk. When your communication layer is centralized enough that one fault freezes hundreds of trains across an entire country, you have a single point of failure for an important national infrastructure.

Whether Tuesday’s outage was a technical failure, a configuration error, a software bug, or something else entirely, Deutsche Bahn hasn’t said. The cause was “identified,” they confirmed. Then nothing. That kind of silence after an event this visible is either operational caution or something they’d rather not headline.

For a deeper look at how railway communication protocols expose critical infrastructure to exactly these kinds of cascading failures, see our analysis of CBTC vulnerabilities and rail network attack surfaces.

Context That Makes This Worse

Germany’s rail network has been struggling. Punctuality has declined for years. Deutsche Bahn is midway through a major infrastructure rebuilding program, trying to catch up after extended underinvestment. These upgrades are disruptive by design but are supposed to improve things long-term.

What Germany has not seen before, at least not from technical causes, is a nationwide train stoppage. Past full-network halts have been storm-related. Bad weather is something passengers can see coming and contextualize. A silent IT failure at midnight is harder to process.

The incident landed in an already skeptical environment. Public confidence in the network is not high. A communications blackout that takes every train in the country offline for two and a half hours, with no explanation of what went wrong, doesn’t help.

What’s Still Unanswered

Deutsche Bahn says the issue is resolved. Services are resuming. The cause was found.

But they haven’t said what the cause was. They haven’t said whether this type of failure can happen again, or what’s being done to prevent it. They haven’t said whether the “emergency system” Palla referenced is a documented fallback or something improvised under pressure.

For a communications failure on this scale, that’s a lot of open questions.

GSM-R is scheduled for eventual replacement by FRMCS, the Future Railway Mobile Communication System, which runs on 4G/5G infrastructure. That migration is underway across Europe but will take years to complete. In the meantime, every European railway operator running on GSM-R is exposed to the same failure mode Germany just experienced.

Tuesday night was a reminder that railway communication infrastructure is exactly the kind of critical system that looks robust until it isn’t.