jerry at hanler.com
Fri May 12 13:16:57 EDT 2017
I sent a note to the site contact this morning asking if they can explain the discrepancy.
More to come.
> On May 12, 2017, at 3:33 AM, Tim Shoppa <tshoppa at gmail.com> wrote:
> I was observing a consistent 5-second discrepancy between real time (GPS,
> WWV, and NTP sources were checked) and time.gov web page last night.
> Round-trip web request/response time between me and time.gov is less than
> This morning it is working fine.
> Note that whenever I drive by the Naval Observatory I try to at least
> glance at my watch and compare it to the big clock too :-). Occasionally
> their LED clock on Mass Ave is off.
> Tim N3QE
> On Thu, May 11, 2017 at 6:09 PM, Donald E. Pauly <trojancowboy at gmail.com>
>> 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.
>> time-nuts mailing list -- time-nuts at febo.com
>> To unsubscribe, go to https://www.febo.com/cgi-bin/
>> and follow the instructions there.
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
More information about the time-nuts