Deutsche Bahn says scheduled maintenance on a central GSM-R component caused the nationwide rail outage that halted passenger and freight traffic across Germany. Brandenburg transport minister Robert Crumbach is demanding full clarification and consequences.

Bahn explanation

Deutsche Bahn says a nationwide rail shutdown that halted passenger and freight traffic across Germany was caused by scheduled maintenance on a central GSM-R communications component.

The outage hit late Tuesday, June 23, and triggered an automatic safety procedure that stopped trains across the network. Service began resuming gradually after midnight, with the first trains running again around 0:30 a.m. on Wednesday, June 24.

AP reported that the operator now says the failure stemmed from maintenance work rather than an unexplained communications collapse. The exact maintenance step that went wrong has not yet been publicly detailed.

What the outage did

The disruption affected Germany's rail-specific GSM-R system, which is used for internal railway communications and operational control. When the fault occurred, safety systems forced trains to stop to prevent unsafe movement.

The shutdown lasted about two hours and stranded passengers across the country. Deutsche Bahn offered taxi and hotel vouchers and, where possible, train space for waiting travelers.

The impact was not limited to passengers. Freight traffic also stopped, adding pressure on a network that is already under scrutiny for reliability and resilience.

Political pressure

Brandenburg transport minister Robert Crumbach has demanded a full explanation from Deutsche Bahn and called for consequences after the outage. WELT reported that he wants complete transparency, stronger redundancy and better emergency management.

His criticism reflects broader concern about how a routine maintenance process could cascade into a nationwide stop. The incident has renewed questions about whether the rail system has enough backup capacity when a central communications component fails.

Reports cited by WELT say security sources do not currently see evidence of sabotage or a cyberattack. That leaves the technical and operational review as the central unanswered issue.

Chronology

The first reports of the disruption emerged late on Tuesday evening, June 23, when train operations were halted nationwide because of a communications problem. Trains started running again step by step after midnight, and AP later reported that Deutsche Bahn had attributed the outage to scheduled maintenance.

That sequence has sharpened attention on the gap between the initial uncertainty and the later explanation. Earlier coverage said the cause had been identified but not disclosed; the newer reporting adds the maintenance-based account.

What comes next

Deutsche Bahn is expected to complete its internal technical review of the failure. The key open question is what exactly in the maintenance process triggered the automatic safety stop and whether procedures need to change.

Regional transport ministers may press for follow-up at future meetings, and the case is likely to remain a test of how the company explains failures on critical infrastructure. The outage has already revived criticism of Deutsche Bahn's reliability and emergency preparedness.

For Germany's rail system, the episode is a reminder that a fault in a central communications layer can halt traffic nationwide within minutes. The next official findings will determine whether the problem is treated as a one-off maintenance mistake or a sign of deeper procedural weakness.

Revision note

Initial automated publication with expanded chronology and accountability context.