SBI Term Loan: RLLR: 8.15 | 7.25% - 8.55%
Canara Bank: RLLR: 8 | 7.15% - 9.85%
ICICI Bank: RLLR: -- | 8.5% - 9.65%
Punjab & Sind Bank: RLLR: 7.3 | 7.35% - 10.75%
Bank of Baroda: RLLR: 7.9 | 7.2% - 8.95%
Federal Bank: RLLR: -- | 7.35% - 9.6%
IndusInd Bank: RLLR: -- | 7.6% - 10%
Bank of Maharashtra: RLLR: 8.05 | 7% - 9.15%
Yes Bank: RLLR: -- | 7.4% - 10.54%
Karur Vysya Bank: RLLR: 8.8 | 8.5% - 10.65%
HDFC Bank: RLLR: -- | 7.75% - 13.2%
Axis Bank: RLLR: -- | 8% - 9.1%
IDBI Bank: RLLR: -- | 7.4% - 10%

Mumbai airport system outage disrupts passenger processing, delays reported across flights

#Hospitality & Retail#Commercial#India#Maharashtra#Mumbai City
Synopsis

A temporary network disruption at Mumbai’s Chhatrapati Shivaji Maharaj International Airport on October 27 affected passenger processing and prompted airport teams to switch to manual procedures. The outage, which reportedly lasted for more than an hour, affected check-in, boarding e-gates and DigiYatra services. Flight-tracking data showed 327 flights delayed by around 9.30 pm, with average departure delays of 50 minutes. The airport operator said teams took steps to maintain essential operations, while the exact number of delays directly attributable to the disruption remained unclear.

A temporary network disruption at Mumbai’s Chhatrapati Shivaji Maharaj International Airport on Tuesday evening, October 27, slowed passenger processing and led airport staff to shift to manual procedures. The outage affected digital systems used for check-in and boarding, including e-gates and DigiYatra facilities, according to reports. 
The disruption reportedly began around 7 pm and lasted for more than an hour. With automated processing affected, airport teams introduced manual measures to keep essential services running and reduce inconvenience to passengers. The change slowed passenger movement through parts of the terminal as staff worked to maintain operations. 
Mumbai International Airport Ltd (MIAL), which operates the airport, confirmed that a temporary network disruption had occurred. The operator said its teams implemented manual processing measures to minimise inconvenience and ensure continuity of essential airport operations. It did not publicly specify the cause of the network issue or provide a detailed account of the systems affected. 
MIAL also maintained that the disruption had not affected airport and flight operations. However, flight-tracking data indicated delays during the same period. According to Flightradar24 figures cited in reports, 327 flights had been delayed by around 9.30 pm, while average departure delays stood at approximately 50 minutes. Around 13 per cent of flights were reported as cancelled. 
The figures cover airport flight movements during the period and do not establish how many delays or cancellations were directly caused by the network outage. The distinction is important because the reported flight delays may also have reflected other operational factors. The airport operator did not provide a breakdown linking individual flights to the technical disruption. 
A separate report focusing on the evening departure window said that 18 of 44 passenger flights scheduled between 7 pm and 9 pm departed at least an hour late, while three were cancelled. These figures relate to a specific time window and should not be treated as directly comparable with the broader count of 327 delayed flights. 
The incident highlighted the operational role of digital systems in passenger processing at a busy metropolitan airport. Manual procedures can help maintain essential services during a technical failure, but they may take longer than automated systems and affect passenger movement through check-in and boarding points. 
The cause of the network disruption and the precise number of flights affected specifically by the outage were not established in the available reports. MIAL did not provide further technical details about the incident. 
Sources: PTI

Discussion

Have something to say? Post your comment