Microsoft 365 Service Status
Official Microsoft 365 service health page.
Live Domain Check
Check if Microsoft Defender is down right now (defender.microsoft.com). Run a live multi-region check to see whether Microsoft Defender is offline for everyone or just you.
Get official Microsoft Defender outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
When Microsoft Defender has instability, teams usually first notice latency spikes and intermittent edge failures rather than a complete blackout.
For Microsoft Defender, early outage signals often show up as TLS handshakes, regional edge routing, and identity federation before a full failure. If results are mixed, use the website outage triage guide, the HTTP status codes guide, and the DNS troubleshooting guide to isolate provider incidents from local network issues.
Use these official Microsoft channels to confirm outages, maintenance notices, and recovery progress for Microsoft Defender.
Official Microsoft 365 service health page.
Official Azure public status dashboard.
Official updates for Microsoft 365 incidents.
Use official Microsoft Defender social profiles to confirm live outage scope, maintenance updates, and recovery progress for defender.microsoft.com.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when defender.microsoft.com seems down. Use this checklist to confirm whether Microsoft Defender is down for everyone or only for you.
Run defender.microsoft.com in WebsiteDown.org first, then open defender.microsoft.com in your own browser. If both checks fail at the same time, Microsoft Defender is likely down beyond your local device.
Check the official Microsoft Defender service status page and compare timestamps with your failed checks.
Test related hosts such as www.microsoft.com, portal.office.com. If they work while defender.microsoft.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for defender.microsoft.com, then share those details with Microsoft Defender support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Microsoft Defender seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open defender.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 defender.microsoft.com. Avoid repeated password or security resets until you confirm this is not a broader Microsoft Defender 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 Defender support.
Run the automatic multi-region check on this page for defender.microsoft.com. If most regions fail at the same time, Microsoft Defender 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 Status, Support, and Live Update Links section above. Start with vendor status and support sources, then compare with live social updates.
Official status dashboards are authoritative but can lag during the first minutes of an incident, so combining both sources gives faster signal.
That pattern usually points to route-specific or account-specific issues rather than a global outage. Common causes include:
Test from a second network and capture the exact error code before resetting credentials.
Use this sequence for defender.microsoft.com: