One question I have is did DOGE decisions have anything to do with this? Because I know they took knives to NIST.
Maybe their generator failing was DOGE related, but wouldn’t have happened if state level shenanigans were better handled
111–120 of 218 posts
One question I have is did DOGE decisions have anything to do with this? Because I know they took knives to NIST.
Maybe their generator failing was DOGE related, but wouldn’t have happened if state level shenanigans were better handled
Earlier quoted context omitted.
If your computer was using it as your time server and you didn't have alternatives configured your clock my have drifted a few seconds.
I never checked it, but how much a typical's pc/server's clock does actually drift over a week or a month? I always thought it's well under a second.
Wind gusts were reaching 125 MPH in Boulder county, if anyone’s curious. A lot of power was shut off preemptively to prevent downed power lines from starting wildfires. Energy providers gave warning to locals in advance. Shame that NIST’s backup generator failed, though.
Notably, we had the marshal fire here 4 years ago and recently Xcel settled for $680M for their role in the fire. So they're probably pretty keen not to be on the hook again
tl;dr - the fire destroyed over 1,000 homes, two deaths. The local electrical utility, Xcel, was found as a contributing cause from sparking power lines during a strong wind storm. As a result, electrical utilities now cut power to affected areas during strong winds.
Earlier quoted context omitted.
If your application is so critical that NTP timing loss causes disaster and your holdover fails in less than a day and you aren't generating your own via gps, you are incompetent, full stop
And if things are that critical, you might have other references besides just GPS...
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
Either go with one clock in your NTPd/Chrony configuration, or ≥4.
Yes, if you have 3 they can triangulate, but if one goes offline now you have 2 with no tie-breaker. If you have (at least) 4 servers, then one can go away and triangulation / sanity-checking can still occur with the 3 remaining.
One question I have is did DOGE decisions have anything to do with this? Because I know they took knives to NIST.
Actually DOGE involvement at the highest level would have resulted in Tesla solar and Tesla powerwall battery backups.
Don't forget Solar Roof.
Earlier quoted context omitted.
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.
Losing NTP for a day is going to affect fuck-all.
Can anybody expand on the implications of this? Being unfamiliar with it, it's hard to tell if this is a minor blip that happens all the time, or if it's potentially a major issue that could cause cascading errors equal to the hype of Y2K.
NIST maintains several time standards. Gaithersburg MD is still up and I assume Hawaii is as well. Other than potential damage to equipment from loss of power (turbo molecular vacuum pumps and oil diffusion pumps might end up failing in interesting ways if not shut down properly) it will just take some time for the clocks to be recalibrated against the other NIST standards.