# Route 53 health check settings

AWS configuration · Updated 17 November 2026

**Short answer:** A Route 53 endpoint health check sends requests from checkers in several Regions every 30 seconds (or 10 seconds at extra cost; the interval can't be changed later) and marks the endpoint unhealthy when it fails the failure threshold of consecutive checks (1 to 10, default 3). The endpoint is healthy only if more than 18% of checkers see it as healthy. HTTP and HTTPS checks need a TCP connection within 4 seconds and a 2xx or 3xx status within 2 more; string matching searches the first 5,120 bytes of the body. Attach checks to failover, weighted or latency records with short TTLs.

## The settings

| Setting (API name) | Values | Default |
|---|---|---|
| Type | HTTP, HTTPS, HTTP_STR_MATCH, HTTPS_STR_MATCH, TCP, CALCULATED, CLOUDWATCH_METRIC, RECOVERY_CONTROL | - |
| Request interval (`RequestInterval`) | 10 or 30 seconds; fixed after creation | 30 |
| Failure threshold (`FailureThreshold`) | 1 to 10 consecutive checks | 3 |
| Resource path, port, FQDN or IP | Endpoint to check | Port 80/443 |
| Search string | Up to 255 characters, must appear in the first 5,120 bytes | - |
| Regions | At least 3 checker Regions (recommended set by default) | Recommended |
| Inverted, Disabled | Flip or pause the result | false |
| Insufficient data status (CloudWatch-alarm checks) | Healthy, Unhealthy, LastKnownStatus | - |

Timing for each checker: HTTP(S) needs a TCP connection within 4 seconds and a 2xx or 3xx within 2 seconds after that; TCP checks need a connection within 10 seconds. HTTPS checks don't validate the certificate, so an expired certificate doesn't fail them.

**Detection time** is roughly interval x failure threshold: 90 seconds with the defaults, 30 seconds with 10-second checks and threshold 3. Add the record TTL for clients to see the change.

## Recommended setup

| Use | Settings |
|---|---|
| Active-passive failover of a public endpoint | HTTPS, 10 s interval, threshold 3, path `/healthz`; record TTL 60 s |
| Cost-sensitive checks of less critical endpoints | 30 s interval, threshold 3 |
| Private resources (not reachable from the internet) | CLOUDWATCH_METRIC check on a CloudWatch alarm, or a calculated check of other checks |
| Several components must all be up | CALCULATED check with `HealthThreshold` set to how many child checks must pass |

The health endpoint must be reachable from the Route 53 health checker IP ranges (published in AWS's IP ranges as service `ROUTE53_HEALTHCHECKS`); a security group or WAF rule that blocks them makes the check fail permanently. Keep the endpoint shallow so a single slow dependency doesn't fail over a healthy Region.

## Create one and attach it

```
aws route53 create-health-check --caller-reference api-eu-2026-11-17 --health-check-config '{
  "Type": "HTTPS", "FullyQualifiedDomainName": "api-eu.example.com", "Port": 443,
  "ResourcePath": "/healthz", "RequestInterval": 10, "FailureThreshold": 3}'

aws route53 get-health-check-status --health-check-id 0a1b2c3d-4e5f-6789-abcd-ef0123456789 \
  --query 'HealthCheckObservations[].[Region,StatusReport.Status]' --output table
```

Then reference the `HealthCheckId` in the primary record of a failover pair (and set `Failover: PRIMARY` / `SECONDARY`). **CloudFormation:** `AWS::Route53::HealthCheck` with `HealthCheckConfig` (`Type`, `FullyQualifiedDomainName`, `ResourcePath`, `RequestInterval`, `FailureThreshold`, `Regions`); records use `HealthCheckId` and `Failover`. **Terraform:** `aws_route53_health_check` (`type`, `fqdn`, `resource_path`, `request_interval`, `failure_threshold`) and `health_check_id` on `aws_route53_record`.

## Monitoring and gotchas

- Health check metrics (`HealthCheckStatus`, `HealthCheckPercentageHealthy`) are published to CloudWatch in **us-east-1** only, so create the [status alarm](https://cloudconsole.dev/alarms/route-53-healthcheckstatus) there whatever Region the endpoint is in.
- Changing the request interval means creating a new health check (CloudFormation replaces it).
- Alias records to load balancers can use `EvaluateTargetHealth` instead of a separate health check.
- Checks are billed per month, more for HTTPS, string matching and fast intervals, and the account default is 200 health checks; see [Route 53 limits](https://cloudconsole.dev/limits/route53-limits).

## Questions

### How often does Route 53 check health?

Every 30 seconds by default, or every 10 seconds if you choose a fast interval. Because many checkers run independently, the endpoint receives requests far more often than that.

### What is the Route 53 health check failure threshold?

The number of consecutive checks an endpoint must fail (or pass) to change status, from 1 to 10. The default is 3.

### Why is my Route 53 health check failing when the site works?

Usually the checker IP ranges are blocked by a security group or firewall, the path returns 4xx or 5xx, or responses take longer than the 4-second connect and 2-second response limits.

## When this happens away from your desk

DNS failover is only useful if you know it happened. CloudConsole, a phone app for AWS, is being built to put health check status alarms on your phone so a failover doesn't go unnoticed.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [How Amazon Route 53 determines whether a health check is healthy](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-determining-health-of-endpoints.html)
- [Values that you specify when you create or update health checks](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-creating-values.html)
- [AWS::Route53::HealthCheck HealthCheckConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-route53-healthcheck-healthcheckconfig.html)

## Related

- [Route 53 TTL settings](https://cloudconsole.dev/config/route53-ttl)
- [Amazon Route 53 limits and quotas](https://cloudconsole.dev/limits/route53-limits)
- [CloudWatch alarm: Route 53 HealthCheckStatus](https://cloudconsole.dev/alarms/route-53-healthcheckstatus)
- [aws route53 change-resource-record-sets](https://cloudconsole.dev/cli/route53-change-resource-record-sets)
- [ALB target group health check settings](https://cloudconsole.dev/config/target-group-health-check-settings)
- [How to check if AWS is down](https://cloudconsole.dev/how-to/check-aws-outage)

---

Source: https://cloudconsole.dev/config/route53-health-checks

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
