Skip to main content
awsdown

Is Amazon Route 53 down?

OperationalLast checked Jul 12, 2026, 4:39 AM UTC

Last 90 days

100% uptime · 0 incidents
2026-04-14: operational2026-04-15: operational2026-04-16: operational2026-04-17: operational2026-04-18: operational2026-04-19: operational2026-04-20: operational2026-04-21: operational2026-04-22: operational2026-04-23: operational2026-04-24: operational2026-04-25: operational2026-04-26: operational2026-04-27: operational2026-04-28: operational2026-04-29: operational2026-04-30: operational2026-05-01: operational2026-05-02: operational2026-05-03: operational2026-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: operational
2026-04-142026-07-12

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