# The time has come: we must enable IPv6 entirely

**URL:** <https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968>\
**Category:** Pool Development\
**Created:** [April 13, 2021, 7:56pm UTC](https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968 "2021-04-13T19:56:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kyle](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@Kyle](https://community.ntppool.org/u/Kyle)\
**Post date:** [April 14, 2021, 7:02am UTC](https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968/2 "2021-04-14T07:02:31Z")

</div>

Just looking at the server count, there appears to be merit in enabling the use of IPv6 on another of the entries. Or maybe not. I will have to do some digging. Right now if everyone was on IPv6 I assume the clients would all prioritize IPv6 for each of the numeric entries, meaning that right now they’d talk to IPv6 servers 25% of the time. Adding one more AAAA record would bring that up to a 50/50 split.

```
             IPv4 IPv6
Africa 37 16
Asia 177 90
Europe 1680 982
North America 632 302
South America 45 12
Oceania 92 36
Global 2660 1426
```

---

_[View the full topic](https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968)._
