# Configure Elastic IP Health Checks

Managed Elastic IPs have an integrated health check. The health check will
periodically run on the attached instances in order to prevent sending ingress
traffic to an instance that is unable to receive it for various reasons, such
as during maintenance or a crash.

The health check can be configured in one of the following modes:

TCP
: check that a TCP connection can be successfully established on a given port.

HTTP
: check that an HTTP request can be successfully performed on a given port and
  URL path. HTTP checks are considered failed if the response status code is
  equal or greater than 400. __Redirects are not followed__.

In either mode, you can further configure the following parameters:

Interval
: the time in seconds to wait between two health check tests (default: 10s)

Timeout
: the time in seconds after which an unresponsive health check test is
  considered failed (default: 2s)

Strikes Fail
: the minimum number of failed tests before considering an instance
  __unhealthy__ (default: 3)

Strikes OK
: the minimum number of successful tests before considering an instance
  __healthy__ (default: 2)

> [!NOTE]
> It is not currently possible to retrieve the health status of an instance. 
> While the system will not direct traffic to an unhealthy instance, the 
> internal state of attached instances is not exposed.

Options for managed Elastic IPv6 prefixes are the same as the IPv4 counterpart.