Fortunately, Microsoft quickly identified the problem and issued a fix within 10 minutes of detecting the error. The company attributed the outage to the certificate update mistake. Reports of the outage continued until beyond 10:00 pm BST before subsiding. However, at around 8:00 am BST the following day, reports started to rise again, though it remains unclear whether this was related to the previous hiccup or a new issue.
