Skip to main content

IPv4 and IPv6 support

Checkly supports both IPv4 and IPv6. We have a dual stack setup, meaning that we can reach both IPv4 and IPv6 addresses from our check runtime. API checks and uptime monitors with an IP family setting (URL, TCP, SSL, ICMP, gRPC and traceroute monitors) connect over IPv4 by default, even when your endpoint is also reachable over IPv6. Set the IP family to IPv6 to connect over IPv6 instead. The check only uses the family you set. For example, an API check that uses IPv4 can’t reach a host name that only has an IPv6 (AAAA) record and fails with a no such host lookup error. With an IPv6 address in the URL, it fails with an error like dial tcp4: address 2001:db8::1: no suitable address found. For other workloads, such as Browser checks, the IPv6 stack is preferred over IPv4: if your endpoint is reachable over IPv6, the check uses IPv6, otherwise it falls back to IPv4. You can actually influence this behaviour in a Browser check by passing the --host-resolver-rules flag to a chromium instance. In the code example below, we force the browser to use IPv4, whereas the host dual.tlund.se is reachable over both IPv4 and IPv6.
resolver.spec.ts

Static IP ranges

All monitoring traffic from Checkly for all customers on all plans comes from a fixed set of source IPs. An up-to-date list can be requested unauthenticated through the API. See our API spec for more info. If you are looking to allowlist Checkly traffic, see our docs on allowlisting.