5 ms·

Wait what?

• snypher 5y ago
  https://developers.google.com/time/smear https://developers.google.com/time/smear
  • aidenn0 5y ago
    For me at least the "wait what" was "when did the google smear leek into general NTP pools," not "what is the google leap second smear"
  • jeffbee 5y ago
    I think the question wasn't about whether Google smears leap seconds on their time service, which has debatable benefits and drawbacks, but rather about your use of "leaked" and "the pool". You should not mix smearing and non-smearing NTP services. I don't believe Google intentionally participates in any NTP pool projects.
    • toast0 5y ago
      I also don't believe google intentionlly participates in pool.ntp.org, but it would be easy for some of the pool servers to have one of google's public ntp servers in their static configuration. On days without a leap second, they're pretty good ntp servers. Personally, I had servers configured with google and some other semi-public servers during the last leap second, and (traditional) ntpd did lots of weird stuff, so I ended up with pretty mushy time that day.
      • brian_cunnie 5y ago
        I have six servers in the pool, and I definitely leaked the Google time smear into the pool. It's hard to get reliable upstream NTP servers--it was easier to point to Google. Google smeared, so my servers smeared, so all my downstream clients smeared. I don't know how much my servers currently handle, but at one point they carried 1% of the North American pool NTP traffic.