Live data from Hacker News

NTP at NIST Boulder Has Lost Power

lists.nanog.org

61–70 of 218 posts

Re: NTP at NIST Boulder Has Lost Power

#61
post #47

This makes me wonder, if you take the average time of all wristwatches on the planet, accounting for timezones and throwing out outliers, how close would you get to NTP time? And how many randomly chosen wristwatches would you need to get anything reasonable?

You’re the person Douglas Adams warned us about.

Re: NTP at NIST Boulder Has Lost Power

#62
post #58

Earlier quoted context omitted.

Tell your friend that this course of action failed, as us in the present are still experiencing issues.

Well, that's _this_ timeline. Other timelines never had an outage.

Not with Terminator rules…

Re: NTP at NIST Boulder Has Lost Power

#64
post #45

Earlier quoted context omitted.

But can't NTP server downtime cause a disaster?

One (amongst many) NTP server going down creates less issues than an NTP server spreading wrong time.

technically if you have 3 or more sources that would be caught; NTP protocol was designed for that eventuality

Re: NTP at NIST Boulder Has Lost Power

#65
post #47

This makes me wonder, if you take the average time of all wristwatches on the planet, accounting for timezones and throwing out outliers, how close would you get to NTP time? And how many randomly chosen wristwatches would you need to get anything reasonable?

I have a hunch my casio wrist watch is designed to be running a bit too quick to make resetting the seconds easier. Your averaging assumes manufacturers try to make their watches as accurate as possible for average conditions

Re: NTP at NIST Boulder Has Lost Power

#66

Earlier quoted context omitted.

One (amongst many) NTP server going down creates less issues than an NTP server spreading wrong time.

technically if you have 3 or more sources that would be caught; NTP protocol was designed for that eventuality

Sure, but not needing a failure to cascade to yet another failsafe is still a good idea. After all, all software has bugs, and all networks have configuration errors.

Re: NTP at NIST Boulder Has Lost Power

#67
post #47

This makes me wonder, if you take the average time of all wristwatches on the planet, accounting for timezones and throwing out outliers, how close would you get to NTP time? And how many randomly chosen wristwatches would you need to get anything reasonable?

You’re the person Douglas Adams warned us about.

Comment of the year.

Re: NTP at NIST Boulder Has Lost Power

#68
post #13

Earlier quoted context omitted.

Google has their own fleet of atomic clocks and time servers. So does AWS. So does Microsoft. So does Ubuntu. They're not going to drift enough for months to cause trouble. So the Internet can ride through this, mostly. The main problem will be services that assume at least one of the NIST time servers is up. Somewhere, there's going to be something that won't work right when all the NIST NTP servers are down. But wh…

I know this is HN, but the internet is pretty low on the list of things NIST time standards are important for.

In a past job I set up at least 5 domain dns servers pointing at nist ntp…

Re: NTP at NIST Boulder Has Lost Power

#69
post #43

Earlier quoted context omitted.

Mostly scientific stuff like astronomical observations — e.g. did this event observed at one telescope coincide with neutrinos detected at this other observatory. Note I didn’t say they are more important than the Internet. That’s a value judgement in any case. I said that NIST level 0 NTp servers are more important to these use cases than they are to the Internet.

All these use at least GPS for timing

No, they don’t. GPS is orders of magnitude less reliable than the most up to date metric time synchronization over fixed topology fiber links.
Post reply on HN