# Leap second 2017 status

**URL:** <https://community.ntppool.org/t/leap-second-2017-status/59>\
**Category:** Uncategorized\
**Created:** [December 31, 2016, 10:04pm UTC](https://community.ntppool.org/t/leap-second-2017-status/59 "2016-12-31T22:04:55Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [January 2, 2017, 2:47am UTC](https://community.ntppool.org/t/leap-second-2017-status/59/10 "2017-01-02T02:47:43Z")

</div>

> [@ghane0](#):
>
> Could this be due to the servers syncing to an upstream server that is implementing leap smearing?

No, those were pretty easy to spot. There [were 9](https://community.ntppool.org/t/google-public-ntp/44/12) in the system (that got kicked out after a few hours).

---

_[View the full topic](https://community.ntppool.org/t/leap-second-2017-status/59)._