> ## Documentation Index > Fetch the complete documentation index at: https://docs.salad.com/llms.txt > Use this file to discover all available pages before exploring further. # Readiness Probes *Last Updated: October 15, 2024* # Overview Readiness probes are only available if [Container Gateway](/container-engine/explanation/infrastructure-platform/networking) or [Job Queues](/container-engine/explanation/job-processing/job-queues) are turned on. They run after the startup probe has completed successfully. They are typically used to evaluate whether the application running in your container is ready to accept traffic. If configured, no traffic will be sent from the load balancer until the readiness probe has passed, so prevent your readiness probe from passing until you have downloaded and warmed up your models. Readiness probes can flap back between passing and failing. If a container's readiness probe reaches the failure state, the container will continue to run on the node but the load balancer will not route any networking traffic. Readiness probe configuration should be fairly strict in order to get that signal out as fast as possible so requests get routed to other nodes.
## Successful Readiness Probe

## Failed Readiness Probe

# Configuration Check the checkbox to enable the readiness probe. Currently, the supported protocols are `exec`, `gRPC`, `TCP`, and `HTTP/1.X`

# Probe Status You can see the status of a readiness probe, if configured, on each instance of a container group.