Monitors & detections
Give IPv4 and IPv6 their own lookout
Choose an address family for endpoint checks and understand what each result means.
Reviewed
Choose the route your owl watches
Open Endpoint monitors, add or edit a monitor and find Address family under Monitor details. Automatic preserves normal address selection. Choose IPv4 only or IPv6 only for HTTP, WebSocket, TLS certificate, TCP or ICMP checks. Automatic ICMP keeps IPv4 for hostnames; a bracketed IPv6 literal uses IPv6.
Save your monitor. To watch both families independently, create two monitors with the same hostname and select one family on each. Each monitor uses one place in your plan allowance.
One family, without a quiet fallback
IPv4 only uses public IPv4 addresses; IPv6 only uses public IPv6 addresses. HTTP redirects keep that choice. If the hostname has no address in the selected family, the check fails and your status confirmation rules apply. An IP-literal URL must match the selected family.
Automatic does not prove that both families work. A successful IPv4 connection can coexist with an IPv6 problem. We still check all returned DNS addresses for public-target safety before choosing the requested family. Private or mixed public/private answers are rejected.
When the lookout cannot reach that network
IPv6 needs a monitoring worker with working IPv6 connectivity. A reported local IPv6 route or address-family failure preserves your last confirmed status instead of opening or resolving an incident. If fresh evidence remains unavailable, the monitor becomes delayed. A timeout alone cannot prove a worker routing problem and follows normal failure confirmation.
Address family chooses IPv4 or IPv6, not a geographic region. DNS record checks have their own A/AAAA rules; heartbeat and domain-expiry monitors do not have this setting. Exports preserve your selection and imports remain paused.