DBS online services down for nearly an hour; second disruption in under 2 months
Sign up now: Get ST's newsletters delivered to your inbox
In response to customer complaints on the bank’s Facebook page and on Twitter, DBS Bank said at about 12.45pm that it was experiencing higher volume traffic for digibank login.
PHOTO: SCREENGRABS FROM POSB, DBS AND DBS/FACEBOOK
Follow topic:
SINGAPORE – Thousands of DBS Bank customers in Singapore said they were unable to use its digibank online and mobile services for about an hour from around 12.30pm on Friday.
DBS’ digital banking services, as well as physical ATMs, were said to be down.
In a statement issued at 2.40pm on Friday, DBS said its digital systems returned to normal at 1.30pm, within 45 minutes from when the disruption was reported.
“Some of our retail customers faced difficulties accessing our banking and payment services, including DBS/POSB digibank online and mobile, DBS Vickers mTrading, DBS PayLah! and ATMs, earlier today,” it said.
In an updated statement at 3.55pm on Friday, DBS said that all its ATMs were up and running.
“Please be assured that our systems are uncompromised, and your monies and deposits remain safe. We are sorry for the inconvenience caused. Thank you for your patience,” said DBS.
In a statement issued at about 9.15pm, the bank said the disruption was caused by a systems issue, and that it was not related to the service disruption that occurred on March 29 or its 5 Million Hawker Meals programme.
The Downdetector website, which tracks service disruptions, saw a surge in complaints about DBS at 12.45pm.
There were more than 2,000 reports from DBS bank customers on the website. At 1pm, nearly 3,000 reports were made.
There were more than 2,000 reports from DBS bank customers on the Downdetector website. At 1pm, nearly 3,000 reports were made.
PHOTO: SCREENGRAB FROM DOWNDETECTOR.SG
Responding on the bank’s Facebook page and on Twitter, DBS said at about 12.45pm that it was experiencing higher volume traffic for digibank login.
Twitter users were also told to e-mail the bank’s customer relations should the problem persist.
Mr Matthew Ng, 24, who works in the finance industry, told The Straits Times that he was unable to access his PayLah! account on Friday morning, even after restarting the app multiple times and switching to the DBS banking app.
He said: “Eventually, I gave up and made payment using another bank app.”
Another user, Mr Zuriel Isaac, said that while queueing up for his lunch around 12pm, he was not able to access DBS’ PayNow service and received a notification saying that there was high traffic.
The 20-year-old full-time national serviceman added: “The service did not work for me after multiple tries, so I decided to use other ways to pay for my lunch instead.”
This is the second disruption reported by the bank’s customers within two months.
On March 29, DBS customers were unable to use digital banking services for more than 12 hours,
The Monetary Authority of Singapore (MAS) described the incident as unacceptable, and said it took seriously the reliability of banks’ critical IT systems.
It added that DBS had fallen short of expectations to maintain the availability of systems at a high level. MAS then instructed DBS to conduct a thorough investigation to establish the root cause of the disruption and submit the findings to the regulator.
Following the March 29 incident, DBS chief executive Piyush Gupta said the bank was disappointed that many of its customers had been unable to access digital banking services.
He added: “We hold ourselves to higher standards, and it is our utmost priority to review the events of today. We acknowledge the gravity of the situation, appreciate our customers’ understanding, and deeply regret the inconvenience caused.”
In November 2021, a malfunctioning access control server disrupted online banking services for DBS and POSB users over three days. It was the bank’s worst digital disruption in a decade.
In response to that incident, MAS imposed an additional capital requirement of $930 million on DBS.
This was four times higher than the $230 million DBS had to set aside for a similar disruption in 2010.

