News for hackers. Stuff that matters.
Re:NIST was 5 μs off UTC after last week's power cut by semenko on Monday December 22, 2025 @04:20PM (#46359239)
I found the most interesting part of the NIST outage post [1] is NIST's special Time Over Fiber (TOF) program [2] that "provides high-precision time transfer by other service arrangements; some direct fiber-optic links were affected and users will be contacted separately."

I've never heard of this! Very cool service, presumably for … quant / HFT / finance firms (maybe for compliance with FINRA Rule 4590 [3])? Telecom providers synchronizing 5G clocks for time-division duplexing [4]? Google/hyperscalers as input to Spanner or other global databases?

Seriously fascinating to me -- who would be a commercial consumer of NIST TOF?

[1] https://groups.google.com/a/list.nist.gov/g/internet-time-se...

[2] https://www.nist.gov/pml/time-and-frequency-division/time-se...

[3] https://www.finra.org/rules-guidance/rulebooks/finra-rules/4...

[4] https://www.ericsson.com/en/blog/2019/8/what-you-need-to-kno...

Re:NIST was 5 μs off UTC after last week's power cut by dmurray on Monday December 22, 2025 @04:34PM (#46359399)
I never saw a need for this in HFT. In my experience, GPS was used instead, but there was never any critical need for microsecond accuracy in live systems. Sub-microsecond latency, yes, but when that mattered it was in order to do something as soon as possible rather than as close as possible to Wall Clock Time X.

Still useful for post-trade analysis; perhaps you can determine that a competitor now has a faster connection than you.

The regulatory requirement you linked (and other typical requirements from regulators) allows a tolerance of one second, so it doesn't call for this kind of technology.

Re:NIST was 5 μs off UTC after last week's power cut by blibble on Monday December 22, 2025 @04:49PM (#46359557)
> I never saw a need for this in HFT. In my experience, GPS was used instead, but there was never any critical need for microsecond accuracy in live systems.

mifid ii (uk/eu) minimum is 1us granularity

https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:...

Re:NIST was 5 μs off UTC after last week's power cut by dmurray on Monday December 22, 2025 @05:21PM (#46359864)
It's 1 us granularity, which means you should report your timestamps with six figures after the decimal point.

The required accuracy (Tables 1 and 2 in that document) is 100 us or 1000 us depending on the system.

Re:NIST was 5 μs off UTC after last week's power cut by blibble on Monday December 22, 2025 @05:52PM (#46360153)
> The required accuracy (Tables 1 and 2 in that document)

no, Tables 1 and 2 say divergence, not accuracy

accuracy is a mix of both granularity and divergence

regardless, your statement before:

> The regulatory requirement you linked (and other typical requirements from regulators) allows a tolerance of one second, so it doesn't call for this kind of technology.

is not true

Re:NIST was 5 μs off UTC after last week's power cut by metaphor on Tuesday December 23, 2025 @02:53AM (#46363338)
> accuracy is a mix of both granularity and divergence

I respectfully disagree.

In context, "granularity" is nothing more than a resolution constraint on reported timestamps. Its inclusion adjacent to the specified "divergence from UTC" is a function of market manipulation surveillance objectives as discussed in preamble item (2), and really doesn't have anything to do with accuracy proper.

Re:NIST was 5 μs off UTC after last week's power cut by broretore on Tuesday December 23, 2025 @08:05PM (#46371328)
any time i am certain of something i never capitalize and i do not end my sentences with periods or use any punctuation because i like people to believe i am an omniscient narrator who cannot be interrupted
Re:NIST was 5 μs off UTC after last week's power cut by throw0101c on Monday December 22, 2025 @09:55PM (#46361909)
> mifid ii (uk/eu) minimum is 1us granularity

1us is nothing special for GPS/NTP/PTP appliances (especially with OCXO/rubidium oscillators):

* https://www.microchip.com/en-us/products/clock-and-timing/sy...

* https://www.meinbergglobal.com/english/productinfo/gps-time-...

Re:NIST was 5 μs off UTC after last week's power cut by goalieca on Monday December 22, 2025 @04:52PM (#46359578)
My guess would be scientific experiments where they need to correlate or sequence data over large regions. Things like correlating gravitational waves with radio signals and gamma ray bursts.
Re:NIST was 5 μs off UTC after last week's power cut by prpl on Monday December 22, 2025 @08:32PM (#46361400)
those are GPS based too. You typically would have a circuit you trained off off 1PPS and hopefully had a 10 or so satellites in view.

You can get 50ns with this. Of course, you would verify at NIST.

Re:NIST was 5 μs off UTC after last week's power cut by YetAnotherNick on Tuesday December 23, 2025 @01:17AM (#46362906)
GPS could be blocked easily, and AFAIK even given corrupted inputs. And HFT could possibly benefit from blocking or corrupting competitors GPS.
Re:NIST was 5 μs off UTC after last week's power cut by johncolanduoni on Tuesday December 23, 2025 @02:44AM (#46363289)
Deploying a GPS jammer in civilized territory is a great way to go to prison.
Re:NIST was 5 μs off UTC after last week's power cut by dotancohen on Tuesday December 23, 2025 @03:58AM (#46363657)
Would it actually go so far?

Would the police actually try to investigate from where came the jammer? Might the competing firm possibly even finance an investigation themselves privately? And if so, would the police then accept the evidence?

People have done far more evil things for money.

Re:NIST was 5 μs off UTC after last week's power cut by johncolanduoni on Tuesday December 23, 2025 @12:00PM (#46366915)
The victim firm would definitely notice, they’d tell the FCC, and their investigators will show up with a device that literally points them to wherever the jammer is. If you do this for stupid, silly reasons you will get fined[1], if you do it in commission of another crime you will probably get made an example of. It doesn’t matter how evil you are, it’s hilariously easy to get caught doing this.

[1]: https://www.nj.com/news/2013/08/man_fined_32000_for_blocking...

Re:NIST was 5 μs off UTC after last week's power cut by dotancohen on Tuesday December 23, 2025 @01:26PM (#46367793)
We are talking about the UK, not the US. And the jammer will most likely be tucked away in some closet with no hint as to how it got there.
Re:NIST was 5 μs off UTC after last week's power cut by johncolanduoni on Tuesday December 23, 2025 @03:14PM (#46368998)
Where were we talking about the UK? All anyone said in this message chain was HFT (and NIST).
Re:NIST was 5 μs off UTC after last week's power cut by dotancohen on Tuesday December 23, 2025 @06:19PM (#46370653)
Sorry, you are correct. As soon as the subject of HFT came up I was thinking about London and the things they do to reduce latency to the exchanges in North America. It's too late to edit or remove my previous message.
Re:NIST was 5 μs off UTC after last week's power cut by MadnessASAP on Tuesday December 23, 2025 @01:55PM (#46368114)
> “Mr. Bojczak claimed that he installed and operated the jamming device in his company-supplied vehicle to block the GPS … system that his employer installed in the vehicle,” the FCC decision stated.

I'm not surprised that somebody would try and do this. However it is just so stupid at every level.

Re:NIST was 5 μs off UTC after last week's power cut by johncolanduoni on Tuesday December 23, 2025 @03:16PM (#46369012)
Next to Newark Airport too. He’s lucky they didn’t throw the book at him - they could’ve hit him for reckless endangerment.
Re:NIST was 5 μs off UTC after last week's power cut by cinntaile on Tuesday December 23, 2025 @03:56AM (#46363644)
It's not like foreign adversaries care.
Re:NIST was 5 μs off UTC after last week's power cut by johncolanduoni on Tuesday December 23, 2025 @11:53AM (#46366848)
The parent was saying HFT firms would do this to other HFT firms. They would care about doing this kind of thing - it’s not a white collar crime. And foreign adversaries would care about doing this during peacetime, especially for very unclear benefit.
Re:NIST was 5 μs off UTC after last week's power cut by metaphor on Tuesday December 23, 2025 @03:06AM (#46363397)
> ...and hopefully had a 10 or so satellites in view.

I believe you'll need 12 GPS sats in view to gain incremental accuracy improvement over 8.

Re:NIST was 5 μs off UTC after last week's power cut by bob1029 on Monday December 22, 2025 @05:49PM (#46360124)
> a commercial consumer

Where does it say these are commercial consumers?

https://en.wikipedia.org/wiki/Schriever_Space_Force_Base#Rol...

> Building 400 at Schriever SFB is the main control point for the Global Positioning System (GPS).

Re:NIST was 5 μs off UTC after last week's power cut by throw0101c on Monday December 22, 2025 @06:21PM (#46360444)
> I've never heard of this! Very cool service, presumably for … quant / HFT / finance firms (maybe for compliance with FINRA Rule 4590 [3])?

To start with, probably for scientific stuff, à la:

* https://en.wikipedia.org/wiki/White_Rabbit_Project

But fibre-based time is important in case of GNSS time signal loss:

* https://www.gpsworld.com/china-finishing-high-precision-grou...

Re:NIST was 5 μs off UTC after last week's power cut by secondcoming on Monday December 22, 2025 @07:48PM (#46361124)
I think Google uses chrony instead of NTP
Re:NIST was 5 μs off UTC after last week's power cut by creatonez on Monday December 22, 2025 @10:29PM (#46362118)
Google doesn't use chrony specifically, just an algorithm that is somewhat chrony-like (but very different in other ways). It's called Google TrueTime.
Re:NIST was 5 μs off UTC after last week's power cut by secondcoming on Tuesday December 23, 2025 @08:01PM (#46371304)
Oh right. Their cloud-init script uninstalls NTP and installs chrony each time our VMs boot
Re:NIST was 5 μs off UTC after last week's power cut by creatonez on Thursday December 25, 2025 @02:07PM (#46386382)
Ah yeah. For VPS tenants it makes sense they would default to Chrony. They have a public facing pool of NTP servers at `time.google.com`, and for tenant use they provide `metadata.google.internal`, which is probably where the Chrony config file points. IIRC TrueTime is not actually open source and is only used internally on their infrastructure.
Re:NIST was 5 μs off UTC after last week's power cut by esseph on Monday December 22, 2025 @07:46PM (#46361114)
I'm sure all of that is true, but so is "Department of Defense".

They're also the largest holder of IPv4 space, still. https://bgp.he.net/report/peers#_ipv4addresses

Re:NIST was 5 μs off UTC after last week's power cut by squigz on Tuesday December 23, 2025 @08:51AM (#46365311)
Why does the DoD hold so many IPv4s?
Re:NIST was 5 μs off UTC after last week's power cut by ErikBjare on Tuesday December 23, 2025 @01:59PM (#46368161)
They were assigned a huge prefix at the creation of the internet iirc
Re:NIST was 5 μs off UTC after last week's power cut by esseph on Tuesday December 23, 2025 @02:23PM (#46368436)
ARPANET, precursor to the internet, was a DoD project.
Re:NIST was 5 μs off UTC after last week's power cut by mmaunder on Monday December 22, 2025 @05:03PM (#46359682)
SIGINT as a source clock for others in a network doing super accurate TDOA for example.
Re:NIST was 5 μs off UTC after last week's power cut by anilakar on Tuesday December 23, 2025 @08:36AM (#46365217)
But they do not need absolute time, and internal rubidium clocks can keep the required accuracy for a few days. After that, sync can be transferred with a portable plug, which is completely viable in tactical/operational level EW systems.
Re:NIST was 5 μs off UTC after last week's power cut by machinationu on Monday December 22, 2025 @06:01PM (#46360245)
science equipment, distributed radio-telescopes where you need to precisely align data received at different locations
Re:NIST was 5 μs off UTC after last week's power cut by ignoramous on Tuesday December 23, 2025 @04:57AM (#46363960)
> Google/hyperscalers as input to Spanner or other global databases?

Think Google might have rolled their own clock sources and corrections.

Ex: Sundial, https://www.usenix.org/conference/osdi20/presentation/li-yul... / https://storage.googleapis.com/gweb-research2023-media/pubto... (pdf)