And this is how really terrible time situations occur.
And this is how really terrible time situations occur.
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.
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.
Since it's not identified as an alternate time scheme on the wire, there's no way for downstream ntpds to know and refuse ut1. Falseticker checks help, but don't eliminate the possibility of following the wrong clock.