Is it down for me?
Testing microsoft365.com from your device…
Outage: Microsoft 365: users may be unable to connect to Exchange Online, Teams, SharePoint and other services. Microsoft is working on a fix.
Read moreMost checked
Not listed? Type its address, like example.com, to check it now.
Microsoft reports an outage. Our last check from one location (UtiBox server · Newark, US) found it answering normally in 515 ms, so the website loads, but parts of Microsoft 365 may not be working.
Testing microsoft365.com from your device…
microsoft365.com loads, but Microsoft reports an outage. Total time to the final page on our latest check.
Thanks, you said it works
1 answer in the last 24 hours · 1 problem report
One answer per person, counted for 24 hours.
No answers in the last 24 hours
Only our server so far. The regional checks run when the page opens.
No posts yet. Be the first to say how Microsoft 365 is working for you.
Our latest check, step by step. Tap a step to open its full record.
Our main check runs from Newark, US. Run the same test from up to 3 internet providers in another country to see whether microsoft365.com is blocked or broken there.
Press Ctrl + Shift + R (⌘ + Shift + R on a Mac).
Rules out extensions and stored cookies.
Move from Wi-Fi to mobile data, or the other way round.
Windows: ipconfig /flushdns · macOS: sudo dscacheutil -flushcache
They can block or reroute requests.
A wrong clock breaks secure connections.
| Date | Problem | Duration | Peak reports | Status |
|---|---|---|---|---|
| Fri 13 Nov, 00:39 UTC | Users may be unable to connect to multiple Microsoft 365 services. | 16 h 18 min | 1/h | Down |
What people say about Microsoft 365, in their own words, kept apart from our own checks.
Live counts · real numbers, refreshed with the page
Posts are public after a quick review. Don’t share personal details or links.
No posts yet.
Be the first to say how Microsoft 365 is working for you.
No posts of this type yet.
That’s every post from the last 30 days.
One answer per person, counted for 24 hours.
Having one of these? Tap it to start a report.
What Microsoft 365 status says about its own service, read from its public status page. A separate signal from our own check and from what people report.
Read from the official feed · the provider last updated it .
What Microsoft 365 status reports about Microsoft’s public Microsoft 365 incidents (organisation-specific issues show only in each organisation’s admin center). A site can answer our own check while the provider reports a problem with one of its features, and the other way round.
Status information is provided by the service operator. UtiBox is independent and isn’t affiliated with Microsoft 365. It may not reflect regional or account-specific problems.
Major impactupdated
Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete. Next update by: Friday, November 13, 2026, at 6:00 PM UTC
No maintenance is planned for Microsoft’s public Microsoft 365 incidents (organisation-specific issues show only in each organisation’s admin center) in the last report we read.
Our first successful read in this window was on 13 Nov 2026.
24 resolved updates since Nov 2026 · 24 major · last one 13 Nov 2026
“Current status: Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete. Next update by: Friday, November 13, 2026, at 6:00 PM UTC”
“Current status: We're observing sustained improvements in service availability as recovery progresses across affected Microsoft 365 services. While service functionality continues to improve, some users may still experience intermittent connectivity issues or delayed email delivery. Our efforts are increasingly focused on resolving the remaining issues and restoring consistent service for all affected users. We're validating recovery across different connection methods and monitoring service stability to confirm that improvements are… Next update by: Friday, November 13, 2026, at 4:00 PM UTC”
“Current status: We're continuing to see improvements in service availability, with email queues significantly reduced and approaching normal levels. Some users may still experience intermittent access issues or delayed email delivery as recovery continues. We've implemented additional mitigation measures and are restoring the remaining affected infrastructure while investigating residual service issues. We're closely monitoring service health and validating recovery across affected connection methods to ensure sustained service… Next update by: Friday, November 13, 2026, at 3:00 PM UTC”
“Current status: We're seeing continued recovery progress across affected regions, with broader improvements now observed in North America and sustained improvements across much of Europe. We're also seeing encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure. Our focus remains on stabilizing recovered infrastructure, completing mitigation in the remaining impacted areas, and… Next update by: Friday, November 13, 2026, at 2:00 PM UTC”
“Current status: We’re seeing encouraging recovery progress in Europe, with service availability and email delivery performance improving across a growing portion of affected Microsoft 365 infrastructure. Japan remains comparatively more stable, while North America is also improving; however, some users may still experience intermittent issues as recovery actions continue. We're focused on addressing the remaining areas of disruption and improving service consistency across affected regions. Reducing email queues and backlogs remains a… Next update by: Friday, November 13, 2026, at 1:00 PM UTC”
“Current status: We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues. Our focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts… Next update by: Friday, November 13, 2026, at 12:00 PM UTC”
“Current status: We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues. Our focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts… Next update by: Friday, November 13, 2026, at 12:00 PM UTC”
“Current status: Recovery actions are ongoing and have progressed in phases across affected Microsoft 365 infrastructure. Global telemetry and customer reports show incremental improvement in several workloads; however, service health remains variable and capacity has not yet fully returned to baseline. Network and traffic-management actions remain active. To protect email during recovery, we’re continuing to prioritize queue and backlog processing, and the email timeout window has been extended to 48 hours to preserve delayed… Next update by: Friday, November 13, 2026, at 11:00 AM UTC”
“Current status: Users may be unable to connect to multiple Microsoft 365 services. Next update by: Friday, November 13, 2026, at 10:00 AM UTC”
“Current status: Users may be unable to connect to multiple Microsoft 365 services.”
“Current status: We’re seeing positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of our infrastructure. We’ll continue to monitor its progress and are working to expand it to servers supporting active regions coming online. As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause… Next update by: Friday, November 13, 2026, at 8:30 AM UTC”
“Current status: We’re continuing to monitor activity across regions to evaluate server status and determine actions that can be taken to improve capacity. This includes reviewing server performance and confirming that developed patches have been applied and working as intended after infrastructure reboots are completed. At this point, we have observed marginal success. In parallel, we’re taking action to expand capacity through the utilization of Virtual Machines. As of now, we are not aware of any malicious activity that is causing… Next update by: Friday, November 13, 2026, at 7:30 AM UTC”
“Current status: As part of our ongoing efforts to advance the recoverability of our frontend servers, we’re evaluating traffic controls that can be applied to increase capacity and stability. This includes traffic optimization actions such as traffic throttling, protocol adjustments, and failover routing intended to improve stability in active regions. In parallel, were expanding internal testing to track activity within a contained environment to improve traffic monitoring and issue detection capabilities. As of now, we are not aware… Next update by: Friday, November 13, 2026, at 7:00 AM UTC”
“Current status: We’re continuing to pursue multiple workstreams to pinpoint the underlying cause of the traffic influx and advance the recoverability of the backend servers. We’re taking a measured approach to identify and repair affected infrastructure to improve the ability to confirm the developed changes were applied. We’re tracking the results of this approach to verify the servers are showing the anticipated recovery and performance intended. As of now, we are not aware of any malicious activity that is causing this incident. We… Next update by: Friday, November 13, 2026, at 7:00 AM UTC”
“Current status: We appreciate your organization’s patience and understanding while we work with urgency to resolve this incident. As we’ve applied our current ongoing mitigation actions, we’ve observed a surge in outbound call volume from our routing services to our backend servers. This occurs when the backend servers outbound service cannot properly route to the backend machines. We’re continuing to observe heightened volume due to traffic rebalancing actions that we have taken throughout this event. We’re working on multiple… Next update by: Friday, November 13, 2026, at 6:00 AM UTC”
“Current status: We’re continuing our efforts to improve server stability to improve traffic flow. This includes adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures. We're observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery, so we're reviewing what additional actions we can take to improve overall infrastructure stability. Next update by: Friday, November 13, 2026, at 5:00 AM UTC”
“Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability. We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions… Next update by: Friday, November 13, 2026, at 4:30 AM UTC”
“Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability. Next update by: Friday, November 13, 2026, at 4:30 AM UTC”
“Current status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances. Next update by: Friday, November 13, 2026, at 3:30 AM UTC”
“Current status: We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions. Next update by: Friday, November 13, 2026, at 3:00 AM UTC”
“Current status: We’re seeing positive results with our efforts to restart affected infrastructure. We’re actively monitoring the performance of these to verify stability which will support improved availability. Remediation actions will be expanded as we confirm stability with the changes applied. Next update by: Friday, November 13, 2026, at 3:00 AM UTC”
“Current status: Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with… Next update by: Friday, November 13, 2026, at 2:00 AM UTC”
“Current status: We've reviewed known impact scenarios and have revised the list of impact services and features, which can be viewed in the "more info" section of this communication. We're continuing our work to isolate the issue affecting server availability, as well as other workstreams. Next update by: Friday, November 13, 2026, at 1:30 AM UTC”
“Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior. Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether… Next update by: Friday, November 13, 2026, at 1:30 AM UTC”
No updates of this kind.
From Microsoft 365 status’s public status history. UtiBox keeps the official updates it reads for 180 days.
At our last check from UtiBox server · Newark, US, Microsoft 365 was up and answering normally. Microsoft reports an outage on its status page, though, so parts of Microsoft 365 may not be working even though the website loads. The page refreshes the check automatically.
The official status page (status.cloud.microsoft) reports “Outage reported” for Microsoft’s public Microsoft 365 incidents (organisation-specific issues show only in each organisation’s admin center), with 1 open incident. We read it every few minutes. It’s separate from our own check of the microsoft365.com website above, so the two can differ.
If it’s up here but not for you, the problem is usually local: your connection, DNS, a browser extension, a VPN or a block on your network. Try the fixes on this page, then the Is It My Internet? check.
Our server requests microsoft365.com and looks at every layer: DNS, the connection, the TLS certificate, the HTTP answer, redirects and the page content. We also check it from up to 12 locations in other countries, using two free probe networks (Globalping and check-host.net), so a regional outage can show here too.
A result is shared for 60 seconds when the site is up and 30 seconds when it has problems, then checked again. You can refresh it yourself after 30 seconds.
Yes. Use “Alert me when it’s back” and we’ll send one email when our check reaches it again. Guests confirm their address first.
UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.
Keep forms secure (ubsid) and remember that you’ve seen this notice (ub_consent). Things you ask us to remember, like light or dark mode and closed banners, are part of this.
UtiBox is free because of ads. Google AdSense and its partners use cookies to show, limit and measure ads. To change how Google personalises the ads you see, use Google’s My Ad Center. To opt out of personalised ads from many companies, visit aboutads.info or youronlinechoices.eu.
Google Analytics counts visits and shows us which pages and tools people use, so we can improve them. It sets _ga cookies. In the EEA, the UK and Switzerland it stores nothing unless you agree. To opt out on any site, use Google’s opt-out browser add-on. Ahrefs Web Analytics counts visits without cookies: it stores nothing on your device and never keeps your IP address; block analytics.ahrefs.com to opt out. Microsoft Clarity records clicks and scrolling for heatmaps and replays, with the tool area and what you type blanked out; block clarity.ms to opt out.