[time-nuts] time.gov

Donald E. Pauly trojancowboy at gmail.com
Thu May 11 18:09:53 EDT 2017


About 10 years ago, I checked my WWVB time code receiver that I built
against time.gov and it was within 0.1 seconds.  That was as close as
the eyeball can tell.  You report a huge error and if confirmed, you
should complain.  I would double check against WWV since WWVB is now
worthless for time comparison.  That webpage is supposed to be
compensated for network delay within 0.1 second.

Just now at 15:00:00 MST I checked my phone with time.gov on wireless
versus a full size computer also on wireless.  I momentarily saw the
phone 65 seconds ahead of the computer.  After hitting refresh and
going off wireless and directly to my carrier, the phone matched the
computer.  I had a witness but cannot get the problem to reappear.  I
don't know exactly why the problem went away.  Some servers may cache
web pages so refresh may be necessary.


---------- Forwarded message ----------
From: Jerry Hancock <jerry at hanler.com>
Date: Thu, May 11, 2017 at 2:36 PM
Subject: [time-nuts] time.gov
To: Discussion of precise time and frequency measurement <time-nuts at febo.com>

I went to time.gov today as I was sitting away from my lab when a new
watch arrived.  Finally got the 25yr watch from the company that laid
me off a week later…

Anyway, I set the seconds rollover to 00 when time.gov reset and then
walked down to my lab and noticed the watch is now 6 seconds slow.  So
I checked again with another computer, same problem, www.time.gov is 6
seconds slow.  Never say this happen, usually it is right on the money
give or take about .2 seconds.


More information about the time-nuts mailing list