[time-nuts] time.gov

David G. McGaw david.g.mcgaw at dartmouth.edu
Fri May 12 04:27:19 UTC 2017


Just tried it, came up 4 sec. slow.  Refreshed the page and it was correct.

David N1HAC


On 5/11/17 7:52 PM, Jerry Hancock wrote:
> I checked it on two different computers and again just now, all were counting 5+ seconds slow.  I then downloaded their flash app which as an option I never had to do and that was correct.  Both of the apps claim to be adjusted for network delay.
>
> This was around 14:00Pacific.  I just checked again and both apps are now correct.  I’ll have to dig into the issue.
>
>
>> On May 11, 2017, at 3:09 PM, Donald E. Pauly <trojancowboy at gmail.com> wrote:
>>
>> https://www.febo.com/pipermail/time-nuts/2017-May/date.html
>>
>> 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.
>>
>> πθ°μΩω±√·Γλ
>> WB0KVV
>>
>> ---------- 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.
>>
>> Jerry
>> _______________________________________________
>> 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.
> _______________________________________________
> 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_lists.febo.com mailing list