Singtel says 16 March outage was caused by mechanical fault and software bugs

Singtel says 16 March outage was caused by mechanical fault and software bugs



 Singtel’s outage on March 16 affected about 600,000 customers and was due to a mechanical fault at one of its network facilities, the telco said on March 19. 

Separately, about 2,000 customers experienced mobile connectivity problems on March 17 because of a software bug from a planned IT system upgrade, Singtel told The Straits Times, revealing details for the first time since the back-to-back outages started.

“We know how important it is to stay connected and recognise the impact these incidents may have had on our customers. This should not have happened. We sincerely apologise,” said Singtel chief executive Ng Tian Chong.

“We are committed to learning from these events and working with our vendors to further enhance our network resilience and improve recovery times.”

For three days in a row, Singtel’s mobile customers faced problems connecting to its network. The eight-hour outage on March 16 caused customers to have “zero bars” of signal on their phones, and disrupted essential services in Singapore, including payments, ride-hailing and food delivery. 

Explaining the event on March 16, Mr Ng said: “Though multiple redundancy measures were in place to support seamless service continuity, our situation required reconfiguration, which took time to fully take effect.”

Although 4G services were restored by around 1.30pm and full 5G restoration was completed around 8pm on the same day, some customers continued to have connection problems the next day.

Explaining what happened on March 17, Mr Ng said the problem caused by the software bug was not immediately apparent as it occurred right after the March 16 disruption. “Once identified, our teams took immediate action and connectivity was progressively restored, with full restoration completed by around 4pm on the same day.”

On March 18, the telco said it had carried out some network reconfigurations to further stabilise and optimise network performance following the two disruptions. It encountered a brief spike in network traffic around 5.30pm during the process, but the problem was resolved in about an hour.



Read Full Article At Source