Notice: Trying to access array offset on value of type bool in /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php on line 44

Notice: Trying to access array offset on value of type bool in /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php on line 45

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768

Warning: Cannot modify header information - headers already sent by (output started at /home3/newsnt8j/public_html/wp-content/plugins/otpless/includes/class-login.php:44) in /home3/newsnt8j/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1768
{"id":92102,"date":"2020-02-04T12:02:55","date_gmt":"2020-02-04T12:02:55","guid":{"rendered":"https:\/\/newsnfeeds.com\/microsoft-teams-outage-was-caused-by-a-really-embarrassing-oversight\/"},"modified":"2020-02-04T12:02:55","modified_gmt":"2020-02-04T12:02:55","slug":"microsoft-teams-outage-was-caused-by-a-really-embarrassing-oversight","status":"publish","type":"post","link":"https:\/\/newsnfeeds.com\/microsoft-teams-outage-was-caused-by-a-really-embarrassing-oversight\/","title":{"rendered":"Microsoft Teams outage was caused by a really embarrassing oversight"},"content":{"rendered":"
\n

Microsoft Teams suffered a lengthy and embarrassing outage yesterday, with the problem caused because Microsoft forgot to renew a security certificate (yes, you read that correctly).<\/p>\n

As The Verge<\/a> reports, Teams was down for a period of around three hours on the morning of February 3.<\/p>\n

The downtime began at around 9am, and just after 11am, a fix was rolled out – with the problem resolved for most people by midday.<\/p>\n