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.
By arn3n 8 hours ago
Somewhat interesting that they themselves don't have access to the site. You'd think there would have been some disaster plans put in place?
By Maxion 8 hours ago
The disater plan is to have a few dozens stratum 1 servers spread around the world, each connected to a distinct primary atomic clock, so that a catastrophic disaster needs to take down the global internet itself for all servers to become unreachable.
The failure of a single such server is far from a disaster.
By cornholio 4 hours ago
For those of us near Boulder, it's urgent.
But the stratum 1 time servers can shrug and route around the damage.
By sounds 2 hours ago
If access to the site is unsafe and thus the site is closed; not having access seems reasonable.
Time services are available from other locations. That's the disaster plan. I'm sure there will be some negative consequences from this downtime, especially if all the Boulder reference time sources lose power, but disaster plans mitigate negative consequences, they can't eliminate them.
Utility power fails, automatic transfer switches fail, backup generators fail, building fires happen, etc. Sometimes the system has to be shut down.
By toast0 an hour ago
Maybe this is the disaster plan: There's not a smouldering hole where NIST's Boulder facility used to be, and it will be operational again soon enough.
There's no present need for important hard-to-replace sciencey-dudes to go into the shop (which is probably both cold, and dark, and may have other problems that make it unsafe: it's deliberately closed) to futz around with the the time machines.
We still have other NTP clocks. Spooky-accurate clocks that the public can get to, even, like just up the road at NIST in Fort Collins (where WWVB lives, and which is currently up), and in Maryland.
This is just one set.
And beyond that, we've also got clocks in GPS satellites orbiting, and a whole world of low-stratum NTP servers that distribute that time on the network. (I have one such GPS-backed NTP server on the shelf behind me; there's not much to it.)
And the orbital GPS clocks are controlled by the US Navy, not NIST.
So there's redundancy in distribution, and also control, and some of the clocks aren't even on the Earth.
Some people may be bit by this if their systems rely on only one NTP server, or only on the subset of them that are down.
And if we're following section 3.2 of RFC 8633 and using multiple diverse NTP sources for our important stuff, then this event (while certainly interesting!) is not presently an issue at all.
By ssl-3 7 hours ago
There are many backup clocks/clusters that NIST uses as redundancies all around Boulder too, no need to even go up to Fort Collins. As in, NIST has fiber to a few at CU and a few commercial companies, last I checked. They're used in cases just like this one.
Fun facts about The clock:
You can't put anything in the room or take anything out. That's how sensitive the clock is.
The room is just filled with asbestos.
The actual port for the actual clock, the little metal thingy that is going buzz, buzz, buzz with voltage every second on the dot? Yeah, that little port isn't actually hooked up to anything, as again, it's so sensitive (impedance matching). So they use the other ports on the card for actual data transfer to the rest of the world. They do the adjustments so it's all fine in the end. But you have to define something as the second, and that little unused port is it.
You can take a few pictures in the cramped little room, but you can't linger, as again, just your extra mass and gravity affects things fairly quickly.
If there are more questions about time and timekeeping in general, go ahead and ask, though I'll probably get back to them a bit later today.
By Balgair 4 hours ago
I'm the Manager of the Computing group at JILA at CU, where utcnist*.colorado.edu used to be housed. Those machines were, for years, consistently the highest bandwidth usage computers on campus.
Unfortunately, the HP cesium clock that backed the utcnist systems failed a few weeks ago, so they're offline. I believe the plan is to decommission those servers anyway - NIST doesn't even list them on the NTP status page anymore, and Judah Levine has retired (though he still comes in frequently). Judah told me in the past that the typical plan in this situation is that you reference a spare HP clock with the clock at NIST, then drive it over to JILA backed by some sort of battery and put it in the rack, then send in the broken one for refurb (~$20k-$40k; new box is closer to $75k). The same is true for the WWVB station, should its clocks fail.
There is fiber that connects NIST to CU (it's part of the BRAN - Boulder Research and Administration Network). Typically that's used when comparing some of the new clocks at JILA (like Jun Ye's strontium clock) to NIST's reference. Fun fact: Some years back the group was noticing loss due to the fiber couplers in various closets between JILA & NIST... so they went to the closets and directly spliced the fibers to each other. It's now one single strand of fiber between JILA & NIST Boulder.
That fiber wasn't connected to the clock that backed utcnist though. utcnist's clock was a commercial cesium clock box from HP that was also fed by GPS. This setup was not particularly sensitive to people being in the room or anything.
Another fun fact: utcnist3 was an FPGA developed in-house to respond to NTP traffic. Super cool project, though I didn't have anything to do with it, haha.
By jrronimo 3 hours ago
This is super cool (and the kind of comment that I love reading on HN!), thanks for sharing.
By mh- an hour ago
>The actual port for the actual clock, the little metal thingy that is going buzz, buzz, buzz with voltage every second on the dot? Yeah, that little port isn't actually hooked up to anything, as again, it's so sensitive (impedance matching). So they use the other ports on the card for actual data transfer to the rest of the world.
Can you restate this part in full technical jargon along with more detail? I'm having a hard time following it
By Workaccount2 4 hours ago
it sounds like there's some kind of coupling, inductive or optoelectronic
As you can see, the room is clearly not filled with asbestos. Furthermore, the claim is absurd on its face. Asbestos was banned in the U.S. in March 2024 [1] and the clock was commissioned in May 2025.
The rest of the claims are equally questionable. For example:
> The actual port for the actual clock ... isn't actually hooked up to anything ... they use the other ports on the card for actual data transfer
It's hard to make heads or tails of this, but if you read the technical description of the clock you will see that by the time you get to anything in the system that could reasonably be described as a "card" with "ports" you are so far from the business end of the clock that nothing you do could plausibly have an impact on its operation.
> You can't put anything in the room or take anything out. That's how sensitive the clock is.
This claim is also easily debunked using the formula for gravitational time dilation [2]. The accuracy of the clock is ~10^-16. Calculating the mass of an object 1m away from the clock that would produce this effect is left as an exercise, but it's a lot more than the mass of a human. To get a rough idea, the relativistic time dilation on the surface of the earth is <100 μs/day [3]. That is huge by atomic clock standards, but that is the result of 10^24kg of mass. A human is 20 orders of magnitude lighter.
Step One of most disaster plans is not to create a second emergency.
By TylerE 7 hours ago
Or even just a microsecond emergency.
By ronjakoi 4 hours ago
Bravo
By f5129cac 3 hours ago
But can't NTP server downtime cause a disaster?
By amelius 7 hours ago
One (amongst many) NTP server going down creates less issues than an NTP server spreading wrong time.
By Vosporos 6 hours ago
General rule of thumb: a misbehaving/slow server in any well-architected distributed system is vastly worse than a dead server.
By macintux 6 hours ago
technically if you have 3 or more sources that would be caught; NTP protocol was designed for that eventuality
By PunchyHamster 6 hours ago
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
By idiotsecant 4 hours ago
And if things are that critical, you might have other references besides just GPS...
By geerlingguy 4 hours ago
Yup, here in Jefferson County - roughly 30 minutes south of Boulder County, we were getting wind gusts around 80mph.
By HaZeust 10 minutes ago
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
By IncreasePosts 5 hours ago
I guess that explains why they had no qualms shutting down half of Boulder's power with a vague time horizon. After losing everything in my fridge, though, they finally turned it back on today.
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.
By tpoindex 3 hours ago
Of the various internet .+P, NTP is one I never learned about as a student, so now I'm looking at its web page [1] by its creator David L. Mills (1938-2024). I've found one video of him giving a retrospective of his extensive internet work; he talks about NTP at 34:51 [2] and later at 56:26 [3].
In [3] he mentions that one can use NTP to observe frequency deviations and use it as an early warning system for fire and AC failure. That really intrigues me. Can you actually? Has this ever been implemented?
By torcete 7 hours ago
Oscillators of all kinds are temperature dependent.
That's why the most stable ones are insulated and ovenized[1].
So an AC failure which would lead to higher room temperatures would lead to stronger or more frequent correction by the NTP client, as the local oscillator would drift more.
Not sure about the fire case though. I mean the same applies there but I'm not imaginative enough to think of a realistic scenario where NTP would be useful for averting a fire.
I knew of some experiments in this space back in the late 1980s or early 1990s - but it was specifically with DECstation hardware that had terrible clocks (not used for alerting, just "this graphs nicely against temperature".) https://groups.csail.mit.edu/ana/Publications/PubPDFs/Greg.T... (PDF) 4.2.1 does talk about explaining local clock frequency changes with office temperature changes (because they overwhelm a clock-aging model) but it doesn't have graphs so perhaps they weren't clear enough to include (or just not relevant enough to Time Surveying.)
By eichin 4 hours ago
What do you mean by +P?
By OptionOfT 4 hours ago
Presumably, .+P is regex referring too all the acronyms ending with P, that is Protocol. SMTP, HTTP, FTP, IMAP, XMPP…
By black_knight 4 hours ago
Looks like .+P is just a regex way of saying any set of characters / protocol ending in P.
By rexreed 4 hours ago
Nothing, as they said .+P (note the dot)
By juped 4 hours ago
> Facility operators anticipated needing to shutdown the heat-exchange infrastructure providing air cooling to many parts of the building, including some internal networking closets. As a result, many of these too were preemptively shutdown with the result that our group lacks much of the monitoring and control capabilities we ordinarily have
Having a parallel low bandwidth, low power, low waste heat network infrastructure for this suddenly seems useful.
By themafia 8 hours ago
NIST campus status: Due to elevated fire risk and a power outage for the Boulder area, the DOC Boulder Labs campus is CLOSED on December 19 for onsite business and no public access is permitted; previously approved accesses are revoked.[1]
WWV still seems to be up, including voice phone access.
NIST Boulder has a recorded phone number for site status, and it says that as of December 20, the site is closed with no access.
NIST's main web site says they put status info on various social media accounts, but there's no announcement about this.
Note that WWV is a good 60 miles NNE of Boulder on the outskirts of Fort Collins.
By Scaevolus 3 hours ago
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.
By cdfuller 9 hours ago
Time travel is extremely dangerous right now. I highly recommend deferring time travel plans except for extreme temporal emergencies.
By autarch 8 hours ago
Uhh, here's the problem, I'm sort of stuck travelling into the future at a more or less constant rate. I don't know how to stop doing that...
By verzali 5 hours ago
Unless you can stop, I'm afraid this will cause almost certain death.
By pbhjpbhj 4 hours ago
Have you tried asymptotically approaching the speed of light?
By lxgr 4 hours ago
I’m quite certain you can approach it in any convenient manner
By jagged-chisel an hour ago
Just go to your local shop and buy some time brakes. That's the safest course of action until this is repaired.
By autarch 4 hours ago
ugh. I have to replace my time rotors again - I thought regen was supposed to help with the wear while it improved range?
By vpribish 2 hours ago
I regret to inform you that as a consequence of that sustained time travel, your mind and body will be slowly deteriorating and you’ll sooner or later end up dead.
By layer8 4 hours ago
Would traveling to the past in order to put in place a preemptive fix for this outage be wise or dangerous?
Asking for a friend.
By jeffrallen 7 hours ago
I couldn't comment on the causal hazards but since time is currently having an outage they've got an improved shot at getting away with it. I say go for it.
By __MatrixMan__ 3 hours ago
Tell your friend that this course of action failed, as us in the present are still experiencing issues.
By ExoticPearTree 7 hours ago
Well, that's _this_ timeline. Other timelines never had an outage.
By autarch 6 hours ago
Not with Terminator rules…
By throwup238 6 hours ago
Safety not guaranteed.
By JadeNB 5 hours ago
Same for database transaction roll back and roll forward actions.
And most enterprises, including banks, use databases.
So by bad luck, you may get a couple of transactions reversed in order of time, such as a $20 debit incorrectly happening before a $10 credit, when your bank balance was only $10 prior to both those transactions. So your balance temporarily goes negative.
Now imagine if all those amounts were ten thousand times higher ...
By fuzztester 7 hours ago
To clear, most banks "sort" transactions from to high to low to create more NSF fees on purpose.
That purpose equates to over $12 billion in fees for 2024
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 what?
By Animats 8 hours ago
Ubuntu using atomic clocks would surprise me. Sure they could, but it's not obvious to me why they would spend $$$$ on such. More plausible to me seems that they would be using GPSDO as reference clocks (in this context, about as good as your own atomic clock), iff they were running their own time servers. Google finds only that they are using servers from the NTP Pool Project, which will be using a variety of reference clocks.
If you have information on what they actually are using internally, please share.
By guenthert 8 hours ago
I think people have a wrong idea of what a modern atomic clock looks like. These are readily available commercially, Microchip for example will happily sell you hydrogen, cesium or rubidium atomic clocks. Hydrogen masers are rather unwieldy, but you can get a rubidium clock in a 1U format and cesium ones are not much bigger. I think their cesium freq standards are formerly a HP business they acquired.
It is also important to realize that an atomic clock will only give you a steady pulse. It will count seconds for you, and do so very accurately, but that is not the same as knowing what time it is.
If you get a rubidium clock for your garage, you can sync it up with GPS to get an accurate-enough clock for your hobby NTP project, but large research institutions and their expensive contraptions are more elaborate to set up.
By xorcist 7 hours ago
There are dedicated turnkey vendors these days, so there's no need to get elaborate. All you need is a U of rack or two and enough cash.
Sure, but F2 is a bit more accurate: "As of February 2016 the IT-CsF2 cesium fountain clock started reporting a uB of 1.7 × 10−16 in the BIPM reports of evaluation of primary frequency standards." ( from https://web.archive.org/web/20220121090046/ftp://ftp2.bipm.o... )
By OhMeadhbh 2 hours ago
atomic clock is not expensive. they have different grades. module level atomic clock cost only $3500.
the NIST hydrogen clock is very expensive and sophisticated.
By ycui1986 37 minutes ago
Atomic clock non-expert here, what does having a fleet of atomic clocks entail and why would the hyperscalers bother?
By genidoi 8 hours ago
Spanner depends on having a time source with bounded error to maintain consistency. Google accomplishes this by having GPS and atomic clocks in several datacenters.
And more importantly, the tighter the time bound, the higher the performance, so more accurate clocks easily pay for themselves in other saved infrastructure costs to service the same number of users.
By londons_explore 7 hours ago
Having clocks synchronized between your servers is extremely useful. For example, having a guarantee that the timestamp of arrival of a packet (measured by the clock on the destination) is ALWAYS bigger than the timestamp recorded by the sender is a huge win, especially for things like database scaling.
For this though you need to go beyond NTP into PTP which is still usually based on GPS time and atomic clocks
By Gabrys1 8 hours ago
Actually interesting to think about what UTC actually means and there is seems to be no absolute source of truth [0]. I guess the worry is not that much about the NTP servers (for which people anyways should configure fail overs) but the clocks themselves.
Could you define an absolute source of truth based on extrinsic features. Something like taking an intrinsic time from atomic sources, pegged to an astronomic or celestial event; then a predicted astronomic event that would allow us to reconcile time in the future.
It might be difficult to generate enough resolution in measurable events that we can predict accurately enough? Like, I'm guessing the start of a transit or alignment event? Maybe something like predicting the time at which a laser pulse will be returnable from a lunar reflector -- if we can do the prediction accurately enough then we can re-establish time back to the current fixed scale.
I think I'm addressing an event that won't ever happen (all precise and accurate time sources are lost/perturbed), and if it does it won't be important to re-sync in this way. But you know...
By pbhjpbhj 4 hours ago
There's a lot of focus in this thread on the atomic clocks but in most datacenters, they're not actually that important and I'm dubious that the hyperscalers actually maintain a "fleet" of them, in the sense that there are hundreds or thousands of these clocks in their datacenters.
The ultimate goal is usually to have a bunch of computers all around the world run synchronised to one clock, within some very small error bound. This enables fancy things like [0].
Usually, this is achieved by having some master clock(s) for each datacenter, which distribute time to other servers using something like NTP or PTP. These clocks, like any other clock, need two things to be useful: an oscillator, to provide ticks, and something by which to set the clock.
In standard off-the-shelf hardware, like the Intel E810 network card, you'll have an OXCO, like [1], with a GPS module. The OXCO provides the ticks, the GPS module provides a timestamp to set the clock with and a pulse for when to set it.
As long as you have GPS reception, even this hardware is extremely accurate. The GPS module provides a new timestamp, potentially accurate to within single-digit nanoseconds ([2] datasheet), every second. These timestamps can be used to adjust the oscillator and/or how its ticks are interpreted, such that you maintain accuracy between the timestamps from GPS.
The problem comes when you lose GPS. Once this happens, you become dependent on the accuracy of the oscillator. An OXCO like [1] can hold to within 1µs accuracy over 4 hours without any corrections but if you need better than that (either more time below 1µs, or more accurate than 1µs over the same time), you need a better oscillator.
The best oscillators are atomic oscillators. [2] for example can maintain better than 200ns accuracy over 24h.
So for a datacenter application, I think the main reason for an atomic clock is simply for retaining extreme accuracy in the event of an outage. For quite reasonable accuracy, a more affordable OXCO works perfectly well.
I don't know about all hyperscalers, but I have knowledge of one of them that has a large enough fleet of atomic frequency standards to warrant dedicated engineering. Several dozen frequency standards at least, possibly low hundreds. Definitely not one per machine, but also not just one per datacenter.
As you say, the goal is to keep the system clocks on the server fleet tightly aligned, to enable things like TrueTime. But also to have sufficient redundancy and long enough holdover in the absence of GNSS (usually due to hardware or firmware failure on the GNSS receivers) that the likelihood of violating the SLA on global time uncertainty is vanishingly small.
The "global" part is what pushes towards having higher end frequency standards, they want to be able to freewheel for O(days) while maintaining low global uncertainty. Drifting a little from external timescales in that scenario is fine, as long as all their machines drift together as an ensemble.
The deployment I know of was originally rubidium frequency standards disciplined by GNSS, but later that got upgraded to cesium standards to increase accuracy and holdover performance. Likely using an "industrial grade" cesium standard that's fairly readily available, very good but not in the same league as the stuff NIST operates.
By dave_universetf 7 minutes ago
I know this is HN, but the internet is pretty low on the list of things NIST time standards are important for.
By adastra22 8 hours ago
But pretty high on the list that NIST NTP is important for (since it leaves the building through the internet).
By willis936 8 hours ago
If NIST NTP goes down, the internet doesn’t go down. But atomic clocks drifting does upset many scientific experiments, which would effectively go down for the duration of the outage.
By adastra22 8 hours ago
This is the reason GP listed out all the alternative robust NTP services that are GPS disciplined, freely available, and used as redundant sources by any responsible timekeeper.
What atomic clocks are disciplined by NTP anyway? Local GPS disciplining is the standard. If you're using NTP you don't need precision or accuracy in your timekeeping.
By willis936 8 hours ago
could you list 3 things that you think are more important than the internet? (I know the internet is going to be fine; I just want to understand what you think ranks higher globally...)
By _zoltan_ 8 hours ago
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.
By adastra22 8 hours ago
All these use at least GPS for timing
By misnome 7 hours ago
The ability for humankind to communicate across the entire globe at nearly 1/4 of the speed of light has drastically accelerated our technological advancement. There is no doubt that the internet is a HUGE addition to society.
It's not super important when compared to basic needs like plumbing, food, electricity, medical assistance and other silly things we take for granted but are heavily dependent on. We all saw what happened to hospitals during the early stages of the COVID pandemic; we had plenty of internet and electricity but were struggling on the medical part. That was quite bad... I'm not sure if it's any worse if an entire country/continent lost access to the Internet. Quite a lot of our core infrastructure components in society rely on this. And a fair bit of it relies on a common understanding of what time "now" is.
By Izmaki 8 hours ago
I think it wont be affected by this but on the top of my head:
- GPS
- industrial complex that synchronize operations (we could include trains)
- telecoms in general (so a level higher than the internet)
By makeitdouble 8 hours ago
GPS uses the atomic clocks on the satellites though.
In a past job I set up at least 5 domain dns servers pointing at nist ntp…
By 2snakes 5 hours ago
Can't they point these dns records to working servers meanwhile to avoid degradation?
By axlee 5 hours ago
My understanding is that people who connect specifically to the NIST ensemble in Boulder (often via a direct fiber hookup rather than using the internet) are doing so because they are running a scientific experiment that relies on that specific clock. When your use case is sensitive enough, it's not directly interchangable with other clocks.
Everyone else is already connecting to load balanced services that rotate through many servers, or have set up their own load balancing / fallbacks. The mistakenly hardcoded configurations should probably be shaken loose anyways.
By creatonez 5 hours ago
GPS?
By dredmorbius 42 minutes ago
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.
By jhart99 7 hours ago
Gaithersburg went down on December 8th, is there confirmation that it's fully functional again?
Time engineers are very paranoid. I expect large problems can't occur due to a single provider misbehaving.
By franklyworks 9 hours ago
>Can anybody expand on the implications of this?
The answer is no. Anyone claiming this will have an impact on infrastructure has no evidence backing it up. Table top exercises at best.
By 1970-01-01 4 hours ago
Unix timestamp resets to zero.
By meindnoch 4 hours ago
I’d say everybody moving off NIST boulder NTP.
By cramcgrab 4 hours ago
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.
By ThrowawayTestr 8 hours ago
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.
By Roark66 7 hours ago
Clocks do drift. Seconds a week is definitely possible. I think there are varying quality of internal clocks in electronic devices, and the cheaper the quality the more drift there is. I think small cheap microcontrollers can drift seconds per day.
By bhouston 5 hours ago
cheap microcontrollers use RC oscillators. If they only drift a few seconds a day, that would be an achievement by itself.
RC oscillator is poor enough that early days USB communication would fail if running on RC clock.
By ycui1986 31 minutes ago
I've seen some new ThinkPads lose a minute a month and others (the old ThinkPads) keep within a second of NTP over an entire year. It depends.
By 1970-01-01 4 hours ago
I have an extremely cheap and extremely low power automatic cat feed - it’s been on 2 D batteries for 18 months. I just reset it after it had drifted 19 minutes, so about 1 minute a month, or 15 seconds a week!
By soared 3 hours ago
Several seconds per week is normal. Oscillator accuracy is roughly on the order of 10 PPM, which would correspond to 6 seconds per week.
By layer8 3 hours ago
FYI, this was posted a month ago when discussing thermal effects of clock drift. I thought it was quite interesting view of what the WWVB location looks like:
Can anybody speak to the current best practices around running underground power lines? I see these types of articles about above-ground distribution systems from time-to-time, particularly in California. I feel lucky that my area has underground power, but that was installed back in the 1980s. Would it be prohibitively expensive for Boulder’s utility provider to move to underground distribution? I can’t help but think it could be worth the cost to reduce wildfire risk and offer more reliable service.
By samch 2 hours ago
Its very hard to repair and keep track of underground.
Think of it like this: overhead power lines require you to dig a 5-7’ deep hole that’s 2’ in diameter every 90’.
Underground power supplied through cable requires you to bury the cable minimum 3’ in the ground in rigid ductwork the entire 90’. Any time that cable runs under a roadway that ductwork needs to be encased in concrete. In urban and semi urban areas you also compete with other buried infrastructure for space - sewer, city/municipal infrastructure, gas, electrical transmission, etc.
While underground distribution systems are less prone to interruption from bad weather it depends on the circuit design. If the underground portion of the circuit is fed from overhead power lines coming from the distribution substation you will still experience interruptions from faults on the overhead. These faults can also occur on overhead transmission circuits (the lines feeding the distribution substations and/or very large industrial customers).
Underground distribution comes at a cost premium compared to overhead distribution. It’s akin to the cost of building a picket fence vs installing a geothermal heating system for your home. This is why new sub divisions will commonly have underground cable installed as the entire neighborhood is being constructed - there’s no need to retrofit underground cable into an existing area and so the costs are lower and borne upfront.
It’s more cost effective for them to turn the power off as a storm rolls through, patrol, make repairs and reenergize then to move everything underground. Lost revenue during that period is a small fraction of the cost of taking an existing grid and rebuilding it underground. This is especially true for transmission circuits that are strung between steel towers over enormous distances.
By pseudonymidy an hour ago
1/3-1/2 of the cost of the electricity we pay is distribution.
Some of it is physical infrastructure (transformers, wire, poles), but a lot of it is labor.
Labor is expensive in US. It’s a lot of labor to do, plus they’ll likely need regulatory approval, buying out land, working through easements.
At the same time you have people screaming about how expensive energy is.
Furthermore they have higher priorities, replacing ancient aging infrastructure that’s crumbling and being put on higher load every day.
By shadowpho an hour ago
My local GPS + PPS based NTP server finally pays off.
By digdigdag an hour ago
One question I have is did DOGE decisions have anything to do with this? Because I know they took knives to NIST.
By sgnelson 4 hours ago
Residents and some businesses of Boulder have been without power since Tuesday. There was an issue about 10 years ago which caused 1000 homes to burn down and the power company was found liable. They change their actions. Then during the next high wind event, the power company preemptively cut power and businesses sued them for loss of revenue. Now the power company is playing it safe and turning off power to residents and keeping downtown businesses powered.
Maybe their generator failing was DOGE related, but wouldn’t have happened if state level shenanigans were better handled
By grepfru_it 3 hours ago
The Marshall fire was 4 years ago. Almost to the day.
By _se 2 hours ago
Actually DOGE involvement at the highest level would have resulted in Tesla solar and Tesla powerwall battery backups.
By cramcgrab 4 hours ago
> […] Tesla solar and Tesla powerwall battery backups.
Don't forget Solar Roof.
By throw0101c 3 hours ago
Any day now
By the_gipsy 3 hours ago
Apparently no engineers here anymore, all armchair politicians.
By cramcgrab an hour ago
Lol, lmao.
Some relevant DOGE’s effects:
-time and frequency division director quit
-NIST emergency management staff at least 50% vacant
-NIST director of safety retired, and NIST safety was already understaffed when compared to DOE labs
-NOAA emergency manager on the same Boulder campus laid off
etc
By redbush237 4 hours ago
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?
By amelius 7 hours ago
You’re the person Douglas Adams warned us about.
By throwup238 6 hours ago
Comment of the year.
By Intermernet 5 hours ago
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
By nielsole 5 hours ago
I think it runs quick to be on the safe side, so you never miss appointments, trains, etc. because of your watch.
But yes, good point.
By amelius 5 hours ago
This is the kind of thing that Casio designers would probably come up with (second to have as much accuracy as possible within their budget)
Given two time changes per year I guess something like 1 min per year is acceptable
By raverbashing 4 hours ago
Close but unlikely to be precise in metrology sense. There's unlikely even a billion wrist watches being worn.
By varjag 6 hours ago
One. One watch. POTUS's watch. And in fact, that's why Boulder is currently shuttered... they disagreed.
It’d be a good idea to protect our infrastructure from the climate we created.
It’s just a good idea, though, not a greedy one… so it won’t happen.
By gilrain 5 hours ago
This was an NTP 0 server right? What is the actual failback mechanism when that level of NTP server fails?
This is some level of eldritch magic that I am aware of, but not familiar with but am interested in learning.
By lovich 8 hours ago
There's two other sites for the time.nist.gov service so it'll be okay.
Probably more interesting is how you get a tier 0 site back in sync - NIST rents out these cyberpunk looking units you can use to get your local frequency standards up to scratch for ~$700/month https://www.nist.gov/programs-projects/frequency-measurement...
By Maxious 7 hours ago
Considering how many servers are in existence, probably the exact same procedure for starting a brand new one?
By 3eb7988a1663 an hour ago
I must have one of those units oh my god
By wpm 4 hours ago
It's like a toaster oven, but it toasts time.
By wat10000 2 hours ago
What happens in the event all the sites for time.nist.gov go down? is it included in the spec?
Also thank you for that link, this is exactly the kind of esoteric knowledge that I enjoy learning about
By lovich 7 hours ago
Most high-availability networks use pool.ntp.org or vendor-specific pools (e.g., time.cloudflare.com, time.google.com, time.windows.com). These systems would automatically switch to a surviving peer in the pool.
Many data centers and telecom hubs use local GPS/GNSS-disciplined oscillators or atomic clocks and wouldn’t be affected.
Most laptops, smartphones, tablets, etc. would be accurate enough for days before drift affected things for the most part.
Kerberos requires clocks to be typically within 5 minutes to prevent replay attacks, so they’d probably be ok.
Sysadmins would need to update hardcoded NTP configurations to point to secondary servers.
If timestamps were REALLY off, TLS certificates might fail, but that’s highly unlikely.
Databases could be corrupted due to failure of transaction ordering.
Financial exchanges are often legally required to use time traceable to a national standard like UTC(NIST). A total failure of the NIST distribution layer could potentially trigger a suspension of electronic trading to maintain audit trail integrity.
Modern power grids use Synchrophasors that require microsecond-level precision for frequency monitoring. Losing the NIST reference would degrade the grid's ability to respond to load fluctuations, increasing the risk of cascading outages.
By sdrmill 7 hours ago
Great list! Just double-checked the CAT timekeeping requirements [1] and the requirement is NIST sync. So a subset of all UTC.
You don’t need to actually sync to NIST. I think most people PTP/PPS to a GPS-connected Grandmaster with high quality crystals.
But one must report deviations from NIST time, so CAT Reporters must track it.
I think you are right — if there is no NIST time signal then there is no properly auditable trading and thus no trading. MFID has similar stuff but I am unfamiliar.
One of my favorite nerd possessions is my hand-signed letter from Judah Levine with my NIST Authenticated NTP key.
There are lots of Stratum 0 servers out there; basically anything with an atomic clock will do. They all count seconds independently from one another, all slowly diverging over time, with offset intervals being measured by mutual synchronization using a number of means (how is this done is interesting all by itself). Some atomic clocks are more accurate than others, and an ensemble of these is typically regarded as 'the' master clock.
Beyond this, as other commenters have said, anyone who is really dependent on having exact time (such as telcos, broadcasters, and those running global synchronized databases) should have their own atomic clock fleets. There are thousands and thousands of atomic clocks in these fleets worldwide. Moreover, GPS time, used by many to act as their time reference, is distributed by yet other means.
Nothing bad will happen, except to those who have deliberately made these specific Stratum 0 clocks their only reference time. Anyone who has either left their computer at its factory settings or has set up their NTP configuration in accordance to recommended settings will be unaffected by this.
By lambdaone 7 hours ago
This is terrible. It’s always sad to hear about things like this.
By jb1991 2 hours ago
Man, they're having a hell of a time up in Boulder.
By qmarchi 9 hours ago
Well, where did NTP at NIST last put it? Did they look there?
By renewiltord 9 hours ago
You misunderstand, there's been a coup
By Y_Y 9 hours ago
Of course there is. Where else would they put the reference standard chickens?
By adastra22 8 hours ago
We have to stop those knaves pushing PTP! NTP must prevail!
By renewiltord 9 hours ago
For future reference of civilization: if a facility is critical, it must have a SMR.
By arn3n 8 hours ago
By Maxion 8 hours ago
By cornholio 4 hours ago
By sounds 2 hours ago
By toast0 an hour ago
By ssl-3 7 hours ago
By Balgair 4 hours ago
By jrronimo 3 hours ago
By mh- an hour ago
By Workaccount2 4 hours ago
By pas 2 hours ago
By lisper 2 hours ago
By ronjakoi 4 hours ago
By mcculley 3 hours ago
By icegreentea2 an hour ago
By TylerE 7 hours ago
By ronjakoi 4 hours ago
By f5129cac 3 hours ago
By amelius 7 hours ago
By Vosporos 6 hours ago
By macintux 6 hours ago
By PunchyHamster 6 hours ago
By idiotsecant 4 hours ago
By geerlingguy 4 hours ago
By HaZeust 10 minutes ago
By IncreasePosts 5 hours ago
By simojo 42 minutes ago
By tpoindex 3 hours ago
By glkindlmann 8 hours ago
By ssl-3 8 hours ago
By torcete 7 hours ago
By magicalhippo 4 hours ago
By eichin 4 hours ago
By OptionOfT 4 hours ago
By black_knight 4 hours ago
By rexreed 4 hours ago
By juped 4 hours ago
By themafia 8 hours ago
By Animats 9 hours ago
By Scaevolus 3 hours ago
By cdfuller 9 hours ago
By autarch 8 hours ago
By verzali 5 hours ago
By pbhjpbhj 4 hours ago
By lxgr 4 hours ago
By jagged-chisel an hour ago
By autarch 4 hours ago
By vpribish 2 hours ago
By layer8 4 hours ago
By jeffrallen 7 hours ago
By __MatrixMan__ 3 hours ago
By ExoticPearTree 7 hours ago
By autarch 6 hours ago
By throwup238 6 hours ago
By JadeNB 5 hours ago
By fuzztester 7 hours ago
By ill13 5 hours ago
By yawpitch 8 hours ago
By Animats 8 hours ago
By guenthert 8 hours ago
By puzzlingcaptcha 7 hours ago
By xorcist 7 hours ago
By badmonkey0001 4 hours ago
By OhMeadhbh 2 hours ago
By ycui1986 37 minutes ago
By genidoi 8 hours ago
By synack 8 hours ago
By londons_explore 7 hours ago
By Gabrys1 8 hours ago
By riedel 7 hours ago
By pbhjpbhj 4 hours ago
By Youden 5 hours ago
By dave_universetf 7 minutes ago
By adastra22 8 hours ago
By willis936 8 hours ago
By adastra22 8 hours ago
By willis936 8 hours ago
By _zoltan_ 8 hours ago
By adastra22 8 hours ago
By misnome 7 hours ago
By Izmaki 8 hours ago
By makeitdouble 8 hours ago
By eichin 4 hours ago
By 2snakes 5 hours ago
By axlee 5 hours ago
By creatonez 5 hours ago
By dredmorbius 42 minutes ago
By jhart99 7 hours ago
By joncrane 3 hours ago
By OhMeadhbh 2 hours ago
By franklyworks 9 hours ago
By 1970-01-01 4 hours ago
By meindnoch 4 hours ago
By cramcgrab 4 hours ago
By ThrowawayTestr 8 hours ago
By Roark66 7 hours ago
By bhouston 5 hours ago
By ycui1986 31 minutes ago
By 1970-01-01 4 hours ago
By soared 3 hours ago
By layer8 3 hours ago
By sgnelson 4 hours ago
By samch 2 hours ago
By tekno45 a minute ago
By pseudonymidy an hour ago
By shadowpho an hour ago
By digdigdag an hour ago
By sgnelson 4 hours ago
By grepfru_it 3 hours ago
By _se 2 hours ago
By cramcgrab 4 hours ago
By throw0101c 3 hours ago
By the_gipsy 3 hours ago
By cramcgrab an hour ago
By redbush237 4 hours ago
By amelius 7 hours ago
By throwup238 6 hours ago
By Intermernet 5 hours ago
By nielsole 5 hours ago
By amelius 5 hours ago
By raverbashing 4 hours ago
By varjag 6 hours ago
By b112 6 hours ago
By 8organicbits 3 hours ago
By DamonHD 7 hours ago
By DamonHD 7 hours ago
By crazydoggers 8 hours ago
By stackghost an hour ago
By gilrain 5 hours ago
By lovich 8 hours ago
By Maxious 7 hours ago
By 3eb7988a1663 an hour ago
By wpm 4 hours ago
By wat10000 2 hours ago
By lovich 7 hours ago
By sdrmill 7 hours ago
By neomantra 5 hours ago
By lambdaone 7 hours ago
By jb1991 2 hours ago
By qmarchi 9 hours ago
By renewiltord 9 hours ago
By Y_Y 9 hours ago
By adastra22 8 hours ago
By renewiltord 9 hours ago
By keepamovin 6 hours ago