Bengaluru metro logs 15 disruptions over 10 months across lines
Data shows Bengaluru’s Namma Metro suffered 15 technical disruptions between September 2025 and July 2026, affecting Purple, Green and Yellow lines. Incidents involved signalling, traction power, train-control and door-closure systems, leading to delays and altered operations.
Key takeaways
- Between September 2025 and July 2026, Bengaluru’s Namma Metro experienced 15 operational disruptions.
- Incidents affected the Purple, Green, and Yellow lines, involving signalling, traction power, and train-control components.
- Root-cause investigations follow major incidents with faulty parts replaced or upgraded to improve reliability.
What Happened
The Namma Metro network in Bengaluru experienced a series of technical disruptions over a 10‑month period, totaling 15 incidents from September 2025 through July 2026. These disruptions affected services on the Purple, Green and Yellow lines. The problems spanned signalling, traction power equipment, train-control components and door-closure verification systems. In some cases, trains were withdrawn from service or movements were adjusted, and at times short-loop operations were used to continue partial service. The episodes prompted authorities to regulate trains and manage passenger flows to mitigate delays.
On the Purple Line, five incidents were recorded. Notable examples include a signalling malfunction near Pattandur Agrahara on September 13, 2025, that caused repeated unintended brake applications, and a June 23 incident involving damage to a third-rail insulator near the Cubbon Park–MG Road section that led to a loss of traction power. In October 2025, a fault involving the main traction power contactor inside a train at Vijayanagar forced the train out of service. A March 15, 2026 interlocking area relay fault caused a signalling power-supply interruption lasting about 25 minutes. A June 3 fault in the door-closing status system prevented traction power from being switched on. On June 11, a wrongly activated protection circuit caused a third-rail power supply fault near the Jalahalli‑Nagasandra/BIEC stretch, with services regulated and some trains operating in short-loop configuration for about 51 minutes. A July 4 third-rail insulator failure near Peenya Industry caused another traction-power loss. On July 9, a cab-door locking mechanism fault prevented the door status from reaching the main controller, hindering normal operations. An onboard signalling and Automatic Train Protection fault between Yeshwanthpur and Jalahalli disrupted normal running and delayed subsequent services.
The Green Line, which runs 33.46 km from Madavara to Silk Institute, accounted for the majority of the cited incidents. Specific Green Line episodes include a May 5 issue where a repetition problem in Automatic Train Operation arose after a driver control-system communication fault linked to a faulty SWI card, and a May 11 door-closing status signal failure at Chickpete, which blocked traction power energisation. A May 5 incident also related to a failure in the driver–control system to communicate with the Automatic Train Control cubicle, tied to a faulty SWI card. On May 11, a door-closing status signal failed to reach the main train controller, inhibiting traction power energisation. A June 11 event involved a misconfigured protection circuit triggering a third-rail power supply fault. A July 9 incident in the same line involved retention of a faulty signal pathway that affected subsequent trains.
On the Yellow Line, three incidents were recorded. A September 22, 2025 event disrupted the reversal arrangement and prevented a train from reaching the Bommasandra terminal. A March 31, 2026 fault involved a burnt contactor coil in a train’s air-conditioning system near HSR Layout–Bommanahalli, after which the train was withdrawn to the depot. A May 18 signalling fault affected train reversal between Bommasandra and Electronics City. These Yellow Line episodes contributed to the overall disruption count.
Officials noted that root-cause investigations are conducted after major incidents, with identified faulty components being replaced or upgraded based on assessments. This process aims to reduce repeat failures and improve reliability across the network.
Why It Matters
Repeated technical faults in a mass transit system can create cascading effects, including longer wait times, train bunching, overcrowding at stations, and disruptions to passenger connections across lines. The combination of signalling failures, power supply issues, and control-system faults can force regulators to alter service patterns, such as switching to short loops or single-line operations for periods of time. The reported incidents underscore ongoing challenges in maintaining complex urban rail infrastructure and the importance of timely maintenance, fault diagnosis, and component upgrades to minimize system-wide ripple effects.
Background
The incidents span multiple major systems within Bengaluru’s metro network, including signalling, traction power, train-control hardware and door-status verification mechanisms. The detailed failures are being examined by the Bengaluru Development Authority and Karnataka state authorities as part of routine fault-analysis and root-cause investigation protocols following major disruptions. The data covers disruptions across the Purple, Green and Yellow lines during the specified 10-month window, with each incident described in terms of location, subsystem affected and operational impact.
Key Facts
- Timeframe of disruptions: September 2025 to July 2026
- Total disruptions reported: 15
- Lines affected: Purple, Green, Yellow
- Major areas of failure: signalling systems, traction power, train-control components, door-closing status systems
- Typical operational impact: delays, trains withdrawn, altered movements, short-loop operations
- Green Line accounted for the largest share of incidents
- Root-cause investigations are standard after major incidents; faulty components are replaced or upgraded as needed
What Happens Next
Authorities indicate that post-incident root-cause investigations are conducted to identify faulty components and implement replacements or upgrades. The ongoing goal is to reduce repeat failures and improve reliability across the network, with adjustments to maintenance and monitoring protocols as needed. Specific next steps beyond the stated investigative framework are not detailed in the available material.
Sources reviewed
Project Chintan independently synthesized and analyzed information cross-checked across the sources listed above.
Related stories
Shantinagara BMTC airport lounge neglected, raising safety concerns
Fire in NICU in Chhindwara hospital kills infant, two others burn
Parking revamp at K.R. Market reshapes flow and small vendor sales
