Is there way to find out in general how many IPv4 and v6 requests the pool (or parts of it) is receiving? Even better if there is change over time stats.
Thanks
1 Like
I’ve looked into this in the past, and my main finding was: it depends on where you are. Some countries generate significantly more IPv6 queries than others. For example, in Germany, the CPE manufacturer AVM has configured 2.pool.ntp.org (the only NTP Pool hostname with AAAA records) as the default in their popular Fritz!Box devices. This has led to a noticeable increase in IPv6-based queries.
I’ve written a small tool that provides a live view of IPv6 vs IPv4 traffic:
ntptools/ntptraf2 at main · mdavids/ntptools · GitHub
For longer-term statistics, you might want to refer to:
- IPv6 – Google
- https://www.facebook.com/ipv6/?tab=ipv6_country
- IPv6 Measurement Maps
- and other similar sources.
Although these resources are not specifically focused on the NTP Pool, they do give a good sense of what might be possible if all NTP Pool hostnames had AAAA records — rather than just one.
Perhaps looking at incoming AAAA DNS queries at the authoritative server level would confirm these statistics, but I’m not able to do that.
1 Like
Oh neat! A few minutes on one of my servers in Norway with maxed netspeed setting:
Afaik, all the major consumer ISPs in Norway have IPv6
After a Ctrl+C:
Some closing stats:
Applied filter: 'udp and port 123'
IPv4 bytes: 131,044,192 (89.327 %), IPv6 bytes: 19,129,440 (10.673 %).
Starttime: Mon Jun 2 01:59:47 2025
Endtime: Mon Jun 2 02:11:46 2025
Total number of packets: 1,629,280.
IPv4: 1,455,376 packets, IPv6: 173,904 packets.
Goodbye!
1 Like
Oh dear… The percentage could’ve been so much higher if only @ask were be willing to add more AAAA records to the pool… 
Rough estimate: you’re only seeing about a quarter of what’s potentially possible — so 44% would actually be achievable?
3 Likes