Frequently asked questions

Check the live answer at the top of our homepage. It re-checks public Azure health data every 60 seconds, and if a service is impaired you will see the affected services and regions, plus a link to the full incident timeline.

We continuously poll the official Azure status page and Azure Service Health, and combine it with our own independent probes and community signals. When impact is confirmed we open an incident and can email subscribers within a minute or two.

No. AzureDown is an independent monitoring site and is not affiliated with, endorsed by, or sponsored by Microsoft. Azure and service names are used only for identification.

Entra ID (formerly Azure Active Directory) is the identity control plane for the whole platform, so when it degrades, sign-ins and token issuance fail across services that are otherwise healthy. A large region such as East US anchors dependencies too, which is why one incident can ripple far beyond the service that broke.

Degraded means elevated errors or latency with partial functionality, so many requests still succeed. An outage means a service or region is substantially unavailable. We roll individual service statuses up to a single overall answer.

We track the major compute, identity, storage, database, and networking services (Virtual Machines, Entra ID, Storage, SQL Database, App Service, AKS, Front Door, Cosmos DB and more) across the commercial Azure regions worldwide.

Our status reflects our own checks plus public Azure health data, so it can differ from, and sometimes lead, Microsoft official dashboard, which is occasionally slow to update. Every incident links back to the official source so you can verify.

Possibly. Azure service SLAs (for example Virtual Machines, SQL Database, and Storage) pay service credits when monthly uptime drops below a threshold. Eligibility depends on the service, the affected region, and your usage. Each of our post-mortems notes likely SLA eligibility.

Credits are not automatic. You generally have to file a claim with evidence within a window of the incident. Work out what you are owed with the independent SLA credit calculator at cloudslacredit.com, or automate breach detection with Next Signal.

Subscribe to free outage alerts. You get one email when an incident is detected, with the affected services and regions, and one when it resolves. You can scope alerts by service, region, and severity.

Our /outages archive has detailed post-mortems of major incidents (timeline, root cause, business impact, SLA eligibility), and every analysis links back to the official Azure status history.

Yes. We maintain plain-language post-mortems of landmark events, explaining what broke, how long it lasted, and what it means for your architecture and your service-credit claims.