About AzureDown

AzureDown answers one question faster and more clearly than anyone else: is Azure down right now? - and then explains what broke, why, and what it means for your SLAs and continuity plan. The site is written for the people accountable for uptime: IT leaders, platform teams, and the engineers who staff the incident bridge.

How status is measured

The status you see is generated by our own ingestion pipeline, which polls Microsoft’s public Azure health data - the RSS feed behind the official Azure status page and the Azure status history - every 60 seconds, maps each event to the services and regions we track, and stores every incident with its update timeline. The live pill on the homepage and the per-service pages on /status reflect the most recent check, with the timestamp shown next to the pill. We do not guess from social media reports.

“Operational” means our latest check found no active incident for that service. Severity levels (advisory / degradation / outage) follow the impact language Azure itself uses, and each service page charts the last 90 days of incident history so a green pill has context.

How post-mortems are researched

Analyses in the outage archive are compiled from primary sources: Microsoft’s official Post Incident Reviews and status-history entries, MSRC publications where relevant, and reproducible technical detail from engineering write-ups. Every post-mortem lists its sources, shows a published and last-updated date, and separates established fact from our analysis. When Microsoft publishes a correction, we update the analysis and bump the visible date.

Who is behind this

AzureDown is operated by the team at Next Signal, whose monitoring platform powers the status checks and the free outage alerts. That relationship is disclosed wherever Next Signal is recommended. AzureDown is not affiliated with, sponsored by, or endorsed by Microsoft; Azure and service names are used for identification.

Corrections

If we got a fact wrong, we want to know. Corrections are applied in place with the last-updated date bumped, so the record is transparent.