We need to perform an urgent maintenance on one of our hosts on Tuesday, 21 January 2014, between 2:45pm and 4:45pm Singapore time. We need to perform an urgent reboot on the host. During this period, servelets hosted on the affected host might need to be rebooted.
We apologise for the inconvenience caused.
On 10 January 2014 since early morning, we detected some network connectivity issue affecting certain servelets hosted in our Singapore cloud infrastructure. An emergency reboot of one of our hosts was being performed to mitigate the problem. Further investigations shows that the problem is caused by network bridge issues affecting one of the hosts, and we have implemented some preventive measures to minimise the impact of the problem.
We apologise for the inconvenience caused.
On 3 January 2014, at around 12:30am SGT (Singapore time), we detected some technical issues on one of our storage nodes in our Singapore cloud infrastructure, causing I/O issue to servelets utilising the node. We performed an urgent maintenance to resolve the issue, and most of the affected servelets are back online by around 5 am SGT.
However, while still in self-healing mode, the storage node experienced problem again at around 4:45pm SGT, and an urgent reboot of the affected servelet node was done, resulting in I/O slowness on some servelets. The storage system was still in self-healing mode after the urgent maintenance, and it’s fully recovered by around 6 pm SGT.
We have performed a full investigation and isolated the root cause of the problem to uneven distribution within the storage system, and we have performed the necessary actions to prevent similar problem from happening in the future.
We apologise for the inconvenience caused.