> How do those other applications obtain the precise value they need without encountering the Internet issue?

They do not use the Internet: they use local (GPS) clocks with internal high-precision clocks for carry-over in case GNSS signal is unavailable:

If those other applications use their own local GPS clocks, what is the significance of NIST (and the 5μs inaccuracy) in their scenario?

	▲	throw0101c an hour ago \| parent \| next [-]
		> If those other applications use their own local GPS clocks, what is the significance of NIST (and the 5μs inaccuracy) in their scenario? Verification and traceability is one reason: it's all very well to claim you're with-in ±x seconds, but your logs may have to say how close you are to the 'legal reality' that is the official time of NIST. NIST may also send out time via 'private fibre' for certain purposes: * https://en.wikipedia.org/wiki/White_Rabbit_Project 'Fibre timing' is also important in case of GNSS signal disruption: * https://www.gpsworld.com/china-finishing-high-precision-grou...
	▲	Denvercoder9 3 hours ago \| parent \| prev [-]
		GPS gets its time from NIST (though during this incident they failed over to another NIST site, so it wasn't impacted).

lysace 7 hours ago | parent | prev [-]

TIL/remembered GNSS satellites have onboard atomic clocks. Makes a lot of sense, but still pretty cool. Something like this, I guess?

	▲	CamperBob2 7 hours ago \| parent [-]
		Yes, either Rb, Cs, or H standards depending on which GNSS system you're using. For the most critical applications, you can license a system like Fugro AtomiChron that provides enhanced GNSS timing down to the level of a few nanoseconds. There are a couple of products that do similar things, all based on providing better ephemerides than your receiver can obtain from the satellites themselves. You can get AtomiChron as an optional subscription with the SparkPNT GPSDO, for instance (https://www.sparkfun.com/sparkpnt-gnss-disciplined-oscillato...).