Is Azure down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, portal.azure.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, portal.azure.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, portal.azure.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, portal.azure.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

That's a common and expected pattern with Azure specifically, because it isn't one monolithic service - it's dozens of independent services running across many separate geographic regions, and an incident is typically scoped to one specific service in one specific region rather than the entire platform. Your app being affected while Azure's overall status looks fine usually means the issue is narrowed to the exact service and region your resources run in.

Yes - these are separately operated services, even within the same region, so an incident affecting Azure Storage doesn't automatically mean Virtual Machines, networking, or other services in that same region are affected. Checking status for the specific service your application depends on is more accurate than assuming a shared status across all of Azure.

Not necessarily. Azure regions are largely independent infrastructure, so an incident in one region, for example East US, commonly has no effect on a different region, such as West Europe, running the same service. Multi-region deployments exist specifically because a single region can have an isolated incident.

Not necessarily. The Azure portal is the web-based management interface, and a portal-specific incident can block configuration changes through the browser without affecting resources that are already running, since those workloads don't depend on the portal staying open to keep operating.