3 ms·An HTTP header caused time.gov to skew from UTC22 points by birdculture 6mo agolanstin 6mo agoNice write up and nice that networking stuff is working well enough that a JavaScript app has to worry about this degree of accuracy.