Microsoft 365 Service Status
Official Microsoft 365 service health page.
Live Domain Check
Check if Microsoft is down right now (microsoft.com). Run a live multi-region check to see whether Microsoft is offline for everyone or just you.
Get official Microsoft outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Microsoft incidents can affect Microsoft 365, Outlook, Teams, Azure, or identity systems independently. Domain checks plus product-specific status pages provide better triage than generic reachability alone.
For Microsoft, incident signals are often feature-specific: Outlook/Teams fail while microsoft.com still loads. Tenant sign-in and auth workflows become intermittent. If this matches what you see on microsoft.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Use both Microsoft 365 service status and Azure Status depending on which Microsoft products are impacted.
Official Microsoft 365 service health page.
Official Azure public status dashboard.
Official updates for Microsoft 365 incidents.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when microsoft.com seems down. Use this checklist to confirm whether Microsoft is down for everyone or only for you.
Run microsoft.com in WebsiteDown.org first, then open microsoft.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Microsoft service status page and compare timestamps with your failed checks.
Test related hosts such as portal.office.com/servicestatus, azure.status.microsoft/status/. If they work while microsoft.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for microsoft.com, then share those details with Microsoft support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Microsoft seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open microsoft.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on microsoft.com. Avoid repeated password or security resets until you confirm this is not a broader Microsoft issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft support.
Run the automatic multi-region check on this page for microsoft.com. If most regions fail at the same time, Microsoft is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether Microsoft is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full Microsoft outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for microsoft.com:
This order helps you avoid unnecessary account resets when the Microsoft issue is provider-side.