# Time.google.com ipv6 in pool

**URL:** <https://community.ntppool.org/t/time-google-com-ipv6-in-pool/1308>\
**Category:** Uncategorized\
**Created:** [July 1, 2019, 11:40pm UTC](https://community.ntppool.org/t/time-google-com-ipv6-in-pool/1308 "2019-07-01T23:40:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nnn](https://avatars.discourse-cdn.com/v4/letter/n/58f4c7/32.png) [@nnn](https://community.ntppool.org/u/nnn)\
**Post date:** [July 1, 2019, 11:40pm UTC](https://community.ntppool.org/t/time-google-com-ipv6-in-pool/1308/1 "2019-07-01T23:40:41Z")

</div>

I was surprised to discover that [2.us.pool.ntp.org](http://2.us.pool.ntp.org) returned 2001:4860:4806:4::, which is apparently in the pool:

```
https://www.ntppool.org/scores/2001:4860:4806:4::

```

Since it implements leap second smearing, it seems like this wouldn’t be consistent with other ntp pool servers… Is this the result of someone accidentally adding [time.google.com](http://time.google.com) to the pool?

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [July 2, 2019, 6:32am UTC](https://community.ntppool.org/t/time-google-com-ipv6-in-pool/1308/2 "2019-07-02T06:32:04Z")

</div>

Thank you; yes – that shouldn’t be there (because Google didn’t add it and yes, because it’s leap smearing). I’ve marked it to not be included in the pool.

(see the other threads about adding validation… ☹)

---

<div class="post-metadata">

**Author:** ![avij](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/avij/32/197_2.png) [@avij](https://community.ntppool.org/u/avij)\
**Post date:** [July 21, 2019, 10:13pm UTC](https://community.ntppool.org/t/time-google-com-ipv6-in-pool/1308/3 "2019-07-21T22:13:01Z")

</div>

Maybe you should give 2001:4860:4806:c:: and 2001:4860:4806:8:: the same treatment as a precaution.