AWS Route 53

What AWS Route 53 actually is

Route 53 is Amazon's managed DNS service: it answers domain-name queries from a global anycast network, translates those queries into routing decisions, and — uniquely among the big DNS providers — ties those decisions to live health checks on your infrastructure. Launched in beta in December 2010 and generally available since May 2011, it is one of the oldest services in the AWS catalog, and the name tells you what it does: Route 53, after TCP/UDP port 53, the port DNS runs on.

The core is conventional: you create a hosted zone for a domain, populate records, and point your registrar's nameservers at the four Route 53 assigns you (deliberately spread across four different TLDs for resilience). What separates Route 53 from a cheap DNS host is the routing layer on top. Simple and weighted routing cover the basics; latency-based routing sends users to the region that answers fastest; geolocation and geoproximity routing pin users to endpoints by geography (useful for data-residency patterns); CIDR-based routing makes decisions on the query's source IP block; and failover routing moves traffic when a health check says an endpoint is down. Health checks themselves are a first-class product: HTTP/HTTPS checks with string matching, fast intervals, latency measurement, calculated and CloudWatch-metric-based checks.

The wider product surface is what keeps AWS shops inside it. Domain registration at per-TLD cost with automatic nameserver association. Alias records that map a zone apex to CloudFront, ELB, or S3 website endpoints without the CNAME-at-apex problem — and, importantly, without query charges. DNSSEC signing for public hosted zones and validation in the Resolver. Route 53 Resolver for hybrid DNS between VPCs, Outposts, and on-premises networks, including conditional forwarding and a Resolver DNS Firewall that filters outbound DNS against domain lists. Traffic Flow, a visual policy editor for global traffic management. Profiles to apply shared configurations across accounts and VPCs. Query logging to CloudWatch.

If you are not on AWS, much of that list is inert. Route 53 is a strong general-purpose DNS host — anyone can point nameservers at it — but its best features (alias records to AWS endpoints, Resolver, health-checked failover into AWS resources) are arguments for staying in the AWS ecosystem, and we should be plain about that.

Pricing: what you really pay

Route 53 publishes a meter table, and every item on it bills separately. Hosted zones: $0.50 per month for each of the first 25, then $0.10 each beyond 25. Standard queries: $0.40 per million for the first billion per month, $0.20 per million above that. Latency-based routing queries: $0.60 per million. Geolocation and geoproximity queries: $0.70 per million. IP-based routing is listed at $0.80 per million. A hosted zone includes up to 10,000 records; records beyond that cost $0.0015 per month each.

Three details on that page deserve attention because they decide whether your bill is trivial or annoying. First, alias records pointing at AWS resources — CloudFront, ELB, S3 website endpoints, API Gateway — answer queries at no charge; using an alias instead of a CNAME for AWS targets can remove the query cost for that record entirely. Second, hosted-zone charges are not prorated: a zone bills on creation and on the first of each month, so infrastructure pipelines that create and destroy zones accumulate fifty-cent charges (the one escape hatch: deleting a zone within 12 hours of creation waives the fee, though its queries still bill). Third, 50 health checks for AWS endpoints in the same account are free for new and existing customers; beyond that, basic health checks run $0.50 per month for AWS endpoints and $0.75 for non-AWS endpoints, with optional features (HTTPS, string matching, fast interval, latency measurement) at $1.00 per month each for AWS endpoints and $2.00 for external ones.

The support meters continue: Route 53 Resolver endpoints at $0.125 per ENI per hour, resolver queries at the standard $0.40 per million (only those passing through an endpoint), and Traffic Flow policy records at $50 per month each. Domain registration is separate and priced per TLD at published rates. AWS GovCloud (US) has its own, higher query table — $0.50 per million standard queries — so government workloads should model against the right page.

What does a real deployment cost? A single domain with a million queries a month and no health checks is under a dollar (one wring.co worked example puts it at $0.90 including the zone). Five domains with 10 million queries and five health checks lands around $8.50 in the same walkthrough; a 50-domain estate with 500 million queries and failover routing reaches the hundreds. The meters are individually cheap and collectively unbounded — the classic AWS pattern — and we would audit unused zones and stale health checks quarterly.

Is the price competitive? Against Cloudflare's free DNS, no — nothing is. Against Google Cloud DNS and Azure DNS, it is in the same band with a genuinely stronger routing and health-check product. For AWS workloads the marginal query cost is usually noise compared to the EC2 bill it serves.

Performance & infrastructure

DNS performance is about answer latency and uptime, and Route 53's architecture addresses both the standard way: a large anycast network answers queries from the location nearest the resolver. The Route 53 features page lists 93 edge locations across North America, Europe, South America, Asia, Australia and New Zealand, and the Middle East and Africa — a broad footprint by any measure, though the exact network is larger than the published list and AWS does not tie DNS answering to specific "regions" the way compute is tied.

Reliability is where Route 53 has its strongest card. The service has carried a 100% availability SLA since general availability in 2011, measured at five-minute intervals, with service credits scaled to the outage: a one-day credit for 5-30 minutes of unavailability, a one-week credit for 31 minutes to four hours, and a one-month credit beyond four hours. We are not aware of another DNS provider publishing a 100% commitment with a defined credit schedule. That does not mean Route 53 never has incidents — no network does — but the paper behind it is the most aggressive in the category, and credit schedules are only worth what their claim process is; AWS's is documented.

Operationally, the anycast design plus four nameservers per zone across four TLDs makes the classic DNS failure modes (registrar trouble, single-registry issues, regional network faults) unlikely to take your names down. DNSSEC closes the cache-poisoning and spoofing classes of attack for zones that enable it. Health-checked failover at five-minute SLA granularity is not instant, but for most application architectures — fail over a web tier, shift weighted records, move a region — it is fast enough, and the integration with CloudWatch metric-based checks means DNS can react to application signals, not just ping results.

We have not benchmarked Route 53's answer latency ourselves (it is outside our current suite — see /benchmarks), so we report the architecture and the published commitments rather than invented millisecond figures.

Where it falls short

Cost creep is the practical complaint. Hosted zones bill whether or not they answer queries, health-check options cost more than the checks themselves, Traffic Flow policy records are $50 a month each, and the per-query surcharges for latency and geo routing mean a sophisticated setup can cost multiples of the naive estimate. The pricing is transparent; it is not simple.

Then there is the blast-radius question. A significant Route 53 outage would be an internet-scale event, and while the SLA is generous, a service credit does not restore your lost traffic. Teams with extreme resilience requirements run secondary DNS (or dual providers) precisely because concentrating every domain on one provider concentrates risk — a point worth making for any DNS provider, and one Route 53's market share makes unusually relevant.

Complexity is the third gap. The console is the AWS console: dozens of features, IAM policies that can lock you out of your own zones, and a learning curve that a solo developer with one domain does not need. Something as simple as the hosted-zone charging model (not prorated, 12-hour delete window) is a footgun documented in a pricing footnote rather than prevented by design. And there is no free tier for the core service — the minimum is a paying hosted zone.

Finally, the anti-alias pattern: the features that make Route 53 compelling — free alias queries, Resolver, health checks against AWS endpoints — are worth little to a shop running on Hetzner or DigitalOcean. For them, the routing policies and the SLA are the product; everything else is someone else's integration story.

Who should pick this

Our pick for AWS workloads that need DNS to make routing decisions, not just resolve names. If you run multi-region architectures, failover between an on-premises site and AWS, or hybrid DNS across VPCs and corporate networks, Route 53's health checks, routing policies, and Resolver are the deepest toolset in the category. It is also the right call when procurement demands a published availability commitment: the 100% SLA with a real credit schedule is what that conversation is asking for.

We would look at /category/dns-providers alternatives when the domain is simple and static — Cloudflare and friends resolve names for less or nothing, and for a brochure site Route 53's meters are more machinery than the job needs. Teams avoiding AWS concentration, or those who want their DNS provider to be their CDN and security vendor, will reasonably choose Cloudflare instead. And anyone automating zone creation should either use the 12-hour delete window discipline or a different provider's API pricing.

Key takeaways

• Managed DNS on a global anycast network (93 listed edge locations) with a 100% availability SLA — measured at 5-minute intervals, with day/week/month service credits.
• Metered pricing: $0.50 per hosted zone/month (first 25), standard queries $0.40 per million, latency routing $0.60, geolocation $0.70 per million; alias queries to AWS resources are free.
• 50 health checks for AWS endpoints are free for all accounts; extra checks are $0.50-$0.75 each with $1-$2 optional features.
• No free tier for the core service, and hosted zones bill without proration — unused zones cost money every month.
• Feature depth is AWS-shaped: health-checked failover, Traffic Flow, Resolver hybrid DNS, DNSSEC, CloudWatch integration.
• Best for multi-region or hybrid AWS architectures needing DNS-based traffic management; overkill for simple static domains.

Sources

• https://aws.amazon.com/route53/pricing
• https://aws.amazon.com/route53/features/
• https://aws.amazon.com/blogs/aws/moving-ahead-with-amazon-route-53
• https://en.wikipedia.org/wiki/Amazon_Route_53
• https://grokipedia.com/page/Amazon_Route_53
• https://wring.co/blog/aws-route53-pricing-guide
• https://costgoat.com/pricing/route-53
• https://akalcloud.ai/blog/route53-cost
• https://c3x.dev/blog/aws-route53-cost-explained
• https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html