Azure Status
Official Azure status across services and regions.
Live Domain Check
Check if Azure is down right now (azure.microsoft.com). Run a live multi-region check to see whether Azure is offline for everyone or just you.
Get official Azure outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Azure outages can affect one region, one identity dependency, or one platform component at a time. This checker helps you decide if failures are local path issues or broader Azure disruption.
For Azure, incident signals are often feature-specific: Initial page load succeeds, then resource API requests errors appear. Portal sign-in and regional resource availability drift out of sync under load. If this matches what you see on azure.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 official sources first, then social/community signals to estimate incident scope and speed of recovery.
Official Azure status across services and regions.
Official support and incident response resources.
Docs for validating service dependencies and fallback design.
Real-time posts and official updates related to Azure incidents.
Official teams often post outage status updates and recovery progress through these social channels.
Recognizing these patterns helps you avoid false assumptions and escalate with better evidence.
Practical steps to follow when azure.microsoft.com seems down. Use this checklist to confirm whether Azure is down for everyone or only for you.
Run azure.microsoft.com in WebsiteDown.org first, then open azure.microsoft.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Azure service status page and compare timestamps with your failed checks.
Test related hosts such as microsoft.com, www.microsoft.com. If they work while azure.microsoft.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for azure.microsoft.com, then share those details with Azure support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Azure seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open azure.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 azure.microsoft.com. Avoid repeated password or security resets until you confirm this is not a broader Azure 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 Azure support.
Run the automatic multi-region check on this page for azure.microsoft.com. If most regions fail at the same time, Azure is likely experiencing a broader outage.
If only one or two regions fail, the issue is usually local to your route, resolver, device state, or account session. Recheck after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use this order so you get reliable signal quickly:
Official dashboards are the source of record, but social channels can surface impact faster in the first minutes of an incident.
That usually means a route-specific or client-specific issue instead of full provider downtime. Common reasons:
Try a private window, switch networks, and compare with this page's regional result before making major local changes.
Use this quick triage sequence:
This keeps your troubleshooting efficient and avoids unnecessary account resets during provider-side incidents.