Skip to main content
azuredown

Is Azure SQL Database down?

OperationalLast checked Aug 1, 2026, 11:52 AM UTC

Last 90 days

100% uptime · 0 incidents
2026-05-04: operational2026-05-05: operational2026-05-06: operational2026-05-07: operational2026-05-08: operational2026-05-09: operational2026-05-10: operational2026-05-11: operational2026-05-12: operational2026-05-13: operational2026-05-14: operational2026-05-15: operational2026-05-16: operational2026-05-17: operational2026-05-18: operational2026-05-19: operational2026-05-20: operational2026-05-21: operational2026-05-22: operational2026-05-23: operational2026-05-24: operational2026-05-25: operational2026-05-26: operational2026-05-27: operational2026-05-28: operational2026-05-29: operational2026-05-30: operational2026-05-31: operational2026-06-01: operational2026-06-02: operational2026-06-03: operational2026-06-04: operational2026-06-05: operational2026-06-06: operational2026-06-07: operational2026-06-08: operational2026-06-09: operational2026-06-10: operational2026-06-11: operational2026-06-12: operational2026-06-13: operational2026-06-14: operational2026-06-15: operational2026-06-16: operational2026-06-17: operational2026-06-18: operational2026-06-19: operational2026-06-20: operational2026-06-21: operational2026-06-22: operational2026-06-23: operational2026-06-24: operational2026-06-25: operational2026-06-26: operational2026-06-27: operational2026-06-28: operational2026-06-29: operational2026-06-30: operational2026-07-01: operational2026-07-02: operational2026-07-03: operational2026-07-04: operational2026-07-05: operational2026-07-06: operational2026-07-07: operational2026-07-08: operational2026-07-09: operational2026-07-10: operational2026-07-11: operational2026-07-12: operational2026-07-13: operational2026-07-14: operational2026-07-15: operational2026-07-16: operational2026-07-17: operational2026-07-18: operational2026-07-19: operational2026-07-20: operational2026-07-21: operational2026-07-22: operational2026-07-23: operational2026-07-24: operational2026-07-25: operational2026-07-26: operational2026-07-27: operational2026-07-28: operational2026-07-29: operational2026-07-30: operational2026-07-31: operational2026-08-01: operational
2026-05-042026-08-01

What Azure SQL Database does - and how it fails

Azure SQL Database runs the managed relational databases behind a large share of enterprise line-of-business applications. SQL incidents hurt disproportionately because the database sits at the bottom of every request path - minutes of connection failures cascade into full application outages, missed batch windows, and SLA conversations with your own customers.

  • Connection failures or login errors to a subset of databases in one region
  • Failovers taking longer than expected on zone-redundant or geo-replicated deployments
  • Elevated query latency from storage or compute degradation underneath the service
  • Control-plane issues blocking scaling, failover, or restore operations while existing connections keep working

Azure SQL Database questions

Is Azure SQL Database down right now?

Check the live status above. If it shows Operational but your database is unreachable, check your connection policy (redirect vs proxy), firewall rules, and whether a recent failover moved your primary to another replica.

What SLA does Azure SQL Database carry?

Business Critical tiers with zone redundancy carry up to a 99.995% monthly availability SLA; General Purpose deployments carry 99.99%. Below the committed target, tiered service credits apply on claim.

Does geo-replication protect me from SQL Database outages?

Active geo-replication and failover groups protect against regional events, but failover is not instant and requires either automation or a decision. Zone redundancy handles single-zone failures transparently - most enterprises need both, mapped to RTO/RPO tiers.

Get alerted when Azure SQL Database breaks

Instant email the moment we detect an incident - affected services and regions included.

Get outage alerts