Magenta Line hit by eight‑hour signalling outage

Delhi’s Magenta Line had one of those failures that sounds technical but feels very physical when you’re stuck inside it. A signalling fault hit the Kalkaji Mandir–Botanical Garden stretch on Tuesday, April 29, and trains on the line spent nearly eight hours crawling instead of running normally. That meant packed platforms, longer waits, and trips that spilled well past the usual rush-hour tolerance. The problem was fixed by about 6 pm, but by then the damage to the day was done. (hindustantimes.com) ### Where did the problem hit? The disruption sat on the Magenta Line section between Kalkaji Mandir and Botanical Garden — a busy link for riders moving across south Delhi and toward Noida. Even when the fault is in one section, metro operations don’t stay neatly boxed there. Trains slow down, spacing changes, and the whole line starts behaving like traffic with one blocked lane. (hindustantimes.com) ### What does a signalling fault actually do? Signalling is the system that tells trains where they are, how far apart they must stay, and how fast they can move safely. When that system misbehaves, the fix is not to “push through.” The safe response is to cut speeds and increase caution. T(hindustantimes.com)a degraded, safety-first mode. (ndtv.com) ### Why did the delays feel so much worse? Because this hit in the middle of the day and dragged into peak travel hours. A short outage is annoying. An eight-hour slowdown is cumulative. One delayed train creates a crowded platform, that crowded platform slows boarding, slow boarding delays the ne(ndtv.com)otal delays stretched toward two hours. (hindustantimes.com) ### What did DMRC say? DMRC put out a service update saying trains were delayed on the Magenta Line because of a signalling issue and that other lines were operating normally. Later, the corporation said the fault had been reported from 10:30 am and rectified by 6 pm. That timing matters because it shows this was not a brief glitch during one rush-hour burst — it was an all-day operational problem on a major corridor. (ndtv.com) ### Was the whole line shut? No — and that distinction matters. The line was disrupted, not fully suspended. Trains continued to run, but at reduced speed and with knock-on delays. For commuters, though, the practical difference can feel small. If a train arrives unpredictably, sits too long, and turns a 35-minute trip into something much longer, the system is functionally failing even if it is technically still open. (hindustantimes.com) ### Why is this more than a bad commute story? Because signalling is the nervous system of a metro. When it breaks, the network’s resilience gets tested in real time. Delhi Metro highlights modern train-control systems as central to reliability and safety, which is exactly why a long signal(hindustantimes.com)tion from overwhelming the rest of a line. (delhimetrorail.com) ### What’s the bottom line? A single signalling fault on April 29 turned a core Delhi Metro corridor into a slow-moving bottleneck for most of the day. Service came back, but the episode showed the catch with high-frequency transit — when control systems falter, the disruption spreads fast and commuters absorb the cost first. (hindustantimes.com)gnalling-issue-101777486080788.html))