Skip to main content
awsdown

Is Amazon Route 53 down?

DegradedLast checked Aug 28, 2026, 5:23 PM UTC

Last 90 days

100% uptime · 0 incidents
2026-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: operational2026-08-02: operational2026-08-03: operational2026-08-04: operational2026-08-05: operational2026-08-06: operational2026-08-07: operational2026-08-08: operational2026-08-09: operational2026-08-10: operational2026-08-11: operational2026-08-12: operational2026-08-13: operational2026-08-14: operational2026-08-15: operational2026-08-16: operational2026-08-17: operational2026-08-18: operational2026-08-19: operational2026-08-20: operational2026-08-21: operational2026-08-22: operational2026-08-23: operational2026-08-24: operational2026-08-25: operational2026-08-26: operational2026-08-27: operational2026-08-28: operational
2026-05-312026-08-28

What Amazon Route 53 does - and how it fails

Amazon Route 53 is AWS’s DNS service, with a 100% availability SLA on the data plane - the strongest commitment in AWS. Even so, control-plane incidents (changes not propagating) and resolver issues do happen, and DNS problems masquerade as outages of everything else.

  • Control-plane delays: record changes and health-check edits not propagating
  • Resolver latency affecting lookups from inside VPCs
  • Health-check false positives triggering unintended failovers
  • Customer-side TTL and negative-caching surprises during incident recovery

Amazon Route 53 questions

Is Route 53 down right now?

The live status above reflects our latest check. Because Route 53’s data plane targets 100% availability, most “DNS is down” reports trace to control-plane delays, resolver latency, or caching artifacts.

What does Route 53’s 100% SLA actually mean?

The 100% commitment covers the authoritative DNS data plane answering queries. If it fails to, credits scale up to 100% of the month’s Route 53 charges - but the control plane (making changes) is not covered by the same target.

Get alerted when Amazon Route 53 breaks

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

Get outage alerts