DE
Donald E. Pauly
Thu, May 11, 2017 10:09 PM
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@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@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
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@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@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
JH
Jerry Hancock
Thu, May 11, 2017 11:52 PM
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@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@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@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@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
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@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@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@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@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
DE
Donald E. Pauly
Thu, May 11, 2017 11:57 PM
Be sure to post your result. Five years ago I regularly checked my
Casio LED watch which was holding 0.3 seconds per week. It always
worked properly. Perhaps we should report this to Trump so he can
fire the head of NIST.
---------- Forwarded message ----------
From: Jerry Hancock jerry@hanler.com
Date: Thu, May 11, 2017 at 4:52 PM
Subject: Re: [time-nuts] time.gov
To: Discussion of precise time and frequency measurement time-nuts@febo.com
Cc: "Donald E. Pauly" trojancowboy@gmail.com
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@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@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@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@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Be sure to post your result. Five years ago I regularly checked my
Casio LED watch which was holding 0.3 seconds per week. It always
worked properly. Perhaps we should report this to Trump so he can
fire the head of NIST.
---------- Forwarded message ----------
From: Jerry Hancock <jerry@hanler.com>
Date: Thu, May 11, 2017 at 4:52 PM
Subject: Re: [time-nuts] time.gov
To: Discussion of precise time and frequency measurement <time-nuts@febo.com>
Cc: "Donald E. Pauly" <trojancowboy@gmail.com>
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@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@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@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@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
DG
David G. McGaw
Fri, May 12, 2017 4:27 AM
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@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@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@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@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
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@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@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@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@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@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
JH
Jerry Hancock
Fri, May 12, 2017 5:41 AM
Since the application takes into account the network speed, maybe there is a cacheing issue initially that is then corrected when you refresh the page? It’s no longer doing it now but was for several hours earlier today.
Strange.
Since the application takes into account the network speed, maybe there is a cacheing issue initially that is then corrected when you refresh the page? It’s no longer doing it now but was for several hours earlier today.
Strange.
TS
Tim Shoppa
Fri, May 12, 2017 10:33 AM
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
100ms.
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@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@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@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@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/
mailman/listinfo/time-nuts
and follow the instructions there.
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
100ms.
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@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@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@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@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/
> mailman/listinfo/time-nuts
> and follow the instructions there.
>
JH
Jerry Hancock
Fri, May 12, 2017 5:16 PM
I sent a note to the site contact this morning asking if they can explain the discrepancy.
More to come.
Jerry
On May 12, 2017, at 3:33 AM, Tim Shoppa tshoppa@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
100ms.
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@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@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@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@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/
mailman/listinfo/time-nuts
and follow the instructions there.
I sent a note to the site contact this morning asking if they can explain the discrepancy.
More to come.
Jerry
> On May 12, 2017, at 3:33 AM, Tim Shoppa <tshoppa@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
> 100ms.
>
> 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@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@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@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@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@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
