Whether you’re using a ping, port or website monitor, FunnyMonitors automatically detects if your host is capable of receiving and transmitting IPv6 traffic. Our monitoring system uses several detection methods to determine the best protocol to use when performing checks.
No additional configuration is required on your side. The protocol detection and selection process happens automatically whenever a monitor runs or reaches its scheduled interval, ensuring your services are tested using the most appropriate network path.
Where IPv6 is available, our system will attempt IPv6 connectivity before falling back to IPv4. This behaviour is visible within your monitor results and allows you to verify that your services are accessible over modern IPv6 networks. Our monitoring requests originate from our own outbound infrastructure using a dedicated /64 IPv6 subnet range.
For environments protected by firewalls, we can provide both our IPv4 and IPv6 monitoring subnets so they can be safely whitelisted. This ensures that monitoring checks can reach your services while maintaining your security policies. Once whitelisted, FunnyMonitors can reliably perform ping, port and website checks without interruption.
This approach allows DevOps teams and system administrators to monitor modern dual-stack infrastructure without extra complexity, ensuring services remain reachable across both IPv4 and IPv6 networks at all times.
Other Providers
Many monitoring providers require you to manually choose whether a monitor should use IPv4 or IPv6. While this approach can work, it also means that if your DNS records change or your infrastructure evolves, you may need to update your monitors to reflect those changes before monitoring continues to function correctly.
At FunnyMonitors, we take a different approach. Our system automatically determines the best IP path for your host and prioritises IPv6 when available, falling back to IPv4 when necessary. This removes the need for manual adjustments and ensures monitoring continues to work even when DNS records or network configurations change.
While all providers aim to follow best practices, these practices are often interpreted differently depending on how monitoring systems are implemented. Some platforms place more responsibility on the user to manage these decisions, which can introduce additional maintenance over time.
Our philosophy is to reduce that burden wherever possible. The more tasks we can automate behind the scenes, the less configuration and maintenance you need to perform to keep monitoring running smoothly.
This approach is especially beneficial in modern environments where infrastructure changes frequently, DNS records are updated regularly and services move between networks. Automatic protocol selection ensures your monitors adapt as your environment evolves.
Ultimately, our goal is to provide reliable monitoring that works intelligently in the background, allowing you to focus on running your services rather than managing how the monitoring system itself operates.
