It would be nice if we got a http(s) monitor that verifies both or selectable ipv4 and IPv6 connections based on the url.
Being able to do anything except ping with ipv6 would be nice.
DNS connection/UDP connection/ etc.
I also recommend to have the ipv6 check support. It’s quite required as loosing ipv6 connectivity is a bit hard to detect.
I had a failure recently where a reconfigured site was not properly enabled for IPv6 (giving a 404) so half the internet was getting an error and half wasn’t - definitely would love this feature in UptimeRobot - thank you!
This would be a very helpful feature, as it’s easy to have an IPv6-only issue go unnoticed now.
Is there any update on this ? having to choose ipv4 or ipv6 would be a nice feature.
In the past we had occurrences where IPv6 DNS Records were incorrect (or servers presented a wrong TLS Cert) thus IPv6 clients were not be able to reach a https site. UptimeRobot can’t notice that reliable at this time.
في الماضي، كانت لدينا حالات حيث كانت سجلات IPv6 DNS غير صحيحة (أو قدمت الخوادم شهادة TLS خاطئة)، وبالتالي لم يتمكن عملاء IPv6 من الوصول إلى موقع https. لا يمكن لـ UptimeRobot ملاحظة أنه يمكن الاعتماد
I do have separate alerts for both IPv4 and IPv6 but these must be specified with IPv6 IP address via http[s]://[xxxx:xxxx::xxxx]/ When checking via DNS, this must check both IPv4 and IPv6 using A and AAAA records respectively. Really the same should probably be true for sites that have a DNS round robin – the problem is more general: suppose you have a site with DNS name xxx.com with several IPs, regardless of IP version. Then a monitor should monitor all these and give a report of which are unavailable. I do this today by having each of the “by IP” entries in as separate monitors, but this wouldn’t work with certain virtual name hosting configuraitons.
UptimeRobot needs to check BOTH IPv4 and IPv6, and not just one. My site supports IPv6, but I need both monitored. IPv6 has ~45% deployment, according to Google. If IPv6 is working fine for my site, but IPv4 is not (affecting ~55% of my customers!), I need to know. This is critical for a monitoring system.
I just had a long period of downtime it took a while to figure out. My site serves on both IPV4 and IPV6. After an upgrade, IPv6 was working, so all of my tests with browsers worked fine, but uptime robot claimed that the site was down. It took me forever to figure out that that was because uptime robot checks Ipv4 only. It would be great if uptime robot reported on both, especially when there is downtime.