21 Breakdowns in 3 Years: What Namma Metro's Reliability Record Really Looks Like

Between January 2024 and June 2026, Namma Metro logged 21 major technical disruptions — roughly one every five to six weeks — spanning signalling failures, power outages, ticketing server crashes, and at least one driverless-train derailment. On June 27, 2026, Bengaluru South MP Tejasvi Surya formally wrote to the Commissioner of Railway Safety and Karnataka's Bengaluru Development Minister, raising five specific concerns and demanding an independent investigation. The letter puts a long-running commuter grievance squarely on the policy agenda.

The 21 incidents: what went wrong, and on which lines

Namma Metro's 21 documented disruptions between 2024 and mid-2026 cover the full spectrum of metro-system vulnerabilities. Incidents include system-wide signalling failures, power supply outages, smart card server crashes that locked commuters out of digital ticketing, door-mechanism faults requiring mid-journey passenger evacuations, and a driverless train derailment on the Yellow Line in January 2026 — the most dramatic single event, though no passengers were injured. A minor fire at Nagasandra station in June 2026 and a June 26 door-locking failure at Cubbon Park — later attributed by BMRCL to a passenger's metal chain lodged in the mechanism — also featured on the list.

The Purple Line, which runs 43.5 km between Whitefield (Kadugodi) and Challaghatta, is the worst-affected corridor, accounting for 11 of the 21 incidents. This matters because the Purple Line carries Namma Metro's highest daily ridership. Each disruption on this corridor ripples into cascading delays across the network — particularly at busy interchange stations like Majestic (Kempegowda), where Green Line connections compound the effect on commuter flow. At-scale reliability problems on the Purple Line are, in effect, system-level reliability problems.

Five posers to BMRCL: what MP Tejasvi Surya is demanding

In his letter of June 27, 2026, Bengaluru South MP Tejasvi Surya addressed both the Commissioner of Railway Safety (Southern Circle) and the Karnataka state minister for Bengaluru development. Surya's five specific demands include: an independent technical investigation into the root causes of recurring failures; a time-bound action plan with milestones for permanent corrective measures; greater transparency from BMRCL about incident reporting; accountability mechanisms for service disruptions during peak travel hours; and a review of the cost-to-commuter equation, given that Namma Metro fares are already among the highest charged by any metro rail system in India.

The letter explicitly frames the issue as a trust deficit: commuters in Bengaluru have limited alternatives to the metro during peak hours and have little recourse when services fail. Surya argues that BMRCL's standard response — 'safety remains a top priority and all incidents are being addressed promptly' — no longer satisfies the public, particularly after 21 disruptions in roughly thirty months of expanded network operation.

What this means for commuters — and what to watch next

For daily riders, the 21-disruption tally is a useful benchmark rather than a verdict. Namma Metro's expanding network is structurally more complex than it was five years ago: more lines, more interchange points, older rolling stock on the original corridors, and a growing proportion of driverless operations on the Yellow Line all raise the probability of an isolated incident. The question is whether BMRCL's maintenance protocols and incident-response systems are scaling with the network. The MP's letter creates pressure for that question to be answered publicly.

The most meaningful near-term signal will be the Commissioner of Railway Safety's response: if CRS requests a formal inspection or audit of BMRCL's maintenance documentation, it marks a shift from reactive to proactive safety oversight. For commuters, the NammaConnect app's live service alert feed remains the fastest way to know when a disruption is happening — and the incident history being publicly documented is, in the long run, the kind of accountability data that should push operators to improve.