Statuspy
Cloud & CDN

Is Microsoft Azure down right now?

Yes — it’s down.

Microsoft Azure appears to be down right now, based on repeated failed checks.

checked responded in 10002ms

Over the last 7 days, Microsoft Azure has answered our automated checks with 5.7% availability and a typical response time of ~1800 ms. The most recent outage began 2026-08-05 04:47 UTC and is still ongoing (severity: down).

Microsoft Azure is the cloud behind much of the enterprise world and Microsoft's own products, including Microsoft 365 and Entra ID. Identity is its highest-impact dependency, so an Entra incident can block sign-in to Teams, Outlook, and customer applications simultaneously while the compute layer is entirely healthy.

Response time (last 24h)
Last 24hpeak 10007 ms
Incident history (last 90 days)
JunJulAug
  • up
  • slow
  • down
  • no reading
DateWhat happenedDurationSeverity
Measured by our checksongoingDown
Uptime
5.7%
7 days
5.7%
30 days
5.7%
90 days
What to do if Microsoft Azure is down for just you
  • Check whether the problem is limited to one region before assuming a global outage, since most cloud incidents are regional.
  • Query a second DNS resolver (1.1.1.1 or 8.8.8.8) to rule out a resolution problem rather than a provider one.
  • Test from a different network or a machine outside the affected region, which separates a routing issue from a service issue.
  • Look at the provider's own per-service dashboard below, as one product can be degraded while everything else is healthy.
Frequently asked questions
Is Microsoft Azure down right now?
Microsoft Azure appears to be down right now, based on repeated failed checks. Last checked 2026-08-05 06:54 UTC (3 minutes ago).
When was Microsoft Azure's last outage?
The most recent outage began 2026-08-05 04:47 UTC and is still ongoing (severity: down).
What should I do if Microsoft Azure is down for me?
Check whether the problem is limited to one region before assuming a global outage, since most cloud incidents are regional. Query a second DNS resolver (1.1.1.1 or 8.8.8.8) to rule out a resolution problem rather than a provider one. Test from a different network or a machine outside the affected region, which separates a routing issue from a service issue. Look at the provider's own per-service dashboard below, as one product can be degraded while everything else is healthy.

Related services