{"id":7332,"date":"2025-10-01T10:03:38","date_gmt":"2025-10-01T10:03:38","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2025\/10\/01\/microsoft-investigating-widespread-outlook-com-outage-preventing-mailbox-access\/"},"modified":"2025-10-01T10:03:38","modified_gmt":"2025-10-01T10:03:38","slug":"microsoft-investigating-widespread-outlook-com-outage-preventing-mailbox-access","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2025\/10\/01\/microsoft-investigating-widespread-outlook-com-outage-preventing-mailbox-access\/","title":{"rendered":"Microsoft Investigating Widespread Outlook.com Outage Preventing Mailbox Access"},"content":{"rendered":"<p>    Microsoft Investigating Widespread Outlook.com Outage Preventing Mailbox Access<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p>Microsoft is actively investigating and addressing widespread errors preventing users from accessing their mailboxes on Outlook.com.<\/p>\n<p>The company has been providing regular updates throughout the day, indicating that targeted infrastructure restarts are gradually restoring service.<\/p>\n<p>The issue, which began early on October 1, 2025, affects users attempting to log in or access their emails via the Outlook.com web interface.<\/p>\n<p>While Microsoft has not detailed the full scope of the impact, user reports suggest a global outage, with many receiving error messages and being unable to view their inboxes.<\/p>\n<p>The root cause has not been officially disclosed, but Microsoft\u2019s response points towards a problem within the service\u2019s underlying infrastructure.<\/p>\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\">\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"embed-twitter\">\n<blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">We have received reports of an issue impacting mailbox connectivity for Consumer and Commercial users. We have determined the cause of the issue to be a degraded subset of service infrastructure. We have rerouted traffic and we&#8217;re monitoring the service to ensure resolution.\u2026<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1973221149019414753?ref_src=twsrc%5Etfw\">October 1, 2025<\/a>\n<\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\n<\/div>\n<\/div>\n<\/figure>\n<h2 class=\"wp-block-heading\" id=\"h-timeline-of-microsoft-s-response\"><strong>Timeline of Microsoft\u2019s Response<\/strong><\/h2>\n<p>Microsoft\u2019s support team has been working to resolve the issue, providing several updates on the service health <a href=\"https:\/\/status.cloud.microsoft\/m365\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">status page<\/a>.<\/p>\n<p>Early in the morning, Microsoft acknowledged the problem and began its investigation. By 10:27 AM (GMT+5:30), the team was applying \u201csmaller targeted reboots of affected infrastructure\u201d and noted a gradual decrease in traffic errors as they monitored the service revert.<\/p>\n<p>Updates around noon confirmed that engineers were continuing to \u201cclosely monitor service availability\u201d and perform \u201cadditional targeted restarts where required.\u201d These actions were aimed at stabilizing the platform and alleviating the impact on users.<\/p>\n<p>By 1:07 PM (GMT+5:30), Microsoft reported observing \u201cimprovements in service availability following our targeted restarts.\u201d The focus shifted to monitoring the service to ensure a full and stable recovery.<\/p>\n<p>The most recent update at 2:33 PM (GMT+5:30) indicated that the team is continuing to see \u201csteady improvements in service availability.\u201d<\/p>\n<p>Furthermore, Microsoft noted that the \u201cbacklog of messages is progressing as expected,\u201d suggesting that email delivery delays that occurred during the outage are also being resolved.<\/p>\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\">\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"embed-twitter\">\n<blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">Since reverting the configuration change, we&#8217;ve observed a steady improvement in service availability. We&#8217;re continuing to closely monitor the service to ensure impact is fully alleviated. More details can be found in the Service Health Dashboard under EX1162980 or\u2026<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1973310698747838829?ref_src=twsrc%5Etfw\">October 1, 2025<\/a>\n<\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\n<\/div>\n<\/div>\n<\/figure>\n<p>While service appears to be returning to normal for many, Microsoft continues to <a href=\"https:\/\/cybersecuritynews.com\/network-monitoring-tools\/\" target=\"_blank\" rel=\"noreferrer noopener\">monitor<\/a> the situation closely to prevent any recurrence and ensure all systems are fully operational.<\/p>\n<p>Users still experiencing issues are advised to check the official Microsoft 365 service status page for the latest information.<\/p>\n<p class=\"has-text-align-center has-background\" style=\"background:linear-gradient(180deg,rgb(238,238,238) 94%,rgb(169,184,195) 100%)\"><strong>Follow us on <a href=\"https:\/\/news.google.com\/publications\/CAAqMggKIixDQklTR3dnTWFoY0tGV041WW1WeWMyVmpkWEpwZEhsdVpYZHpMbU52YlNnQVAB?hl=en-IN&amp;gl=IN&amp;ceid=IN:en\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Google News<\/a>, <a href=\"https:\/\/www.linkedin.com\/company\/cybersecurity-news\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">LinkedIn<\/a>, and <a href=\"https:\/\/x.com\/cyber_press_org\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">X<\/a> for daily cybersecurity updates. <a href=\"https:\/\/cybersecuritynews.com\/contact-us\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Contact us<\/a> to feature your stories.<\/strong><\/p>\n<p>The post <a href=\"https:\/\/cybersecuritynews.com\/widespread-outlook-com-outage\/\">Microsoft Investigating Widespread Outlook.com Outage Preventing Mailbox Access<\/a> appeared first on <a href=\"https:\/\/cybersecuritynews.com\/\">Cyber Security News<\/a>.<\/p>\n<\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><br \/>\n    Guru Baran<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/cybersecuritynews.com\/widespread-outlook-com-outage\/\">Go to cyber-security-news<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft Investigating Widespread Outlook.com Outage Preventing Mailbox Access Microsoft is actively investigating and addressing widespread errors preventing users from accessing their mailboxes on Outlook.com. The company has been providing regular updates throughout the day, indicating that targeted infrastructure restarts are gradually restoring service. The issue, which began early on October 1, 2025, affects users attempting [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63,1535,1440,395],"tags":[130],"class_list":["post-7332","post","type-post","status-publish","format-standard","hentry","category-cyber-security-news","category-outlook","category-tech-news","category-windows","tag-cyber-security-news"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/7332"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=7332"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/7332\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=7332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=7332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=7332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}