John Pettitt wrote:
> I noticed in that a lot of the servers in the pool I've looked at use
> the NIST servers as their upstream - my experience has been that these
> servers are way overloaded and tend to appear rather unstable as a
> result. With that in mind I'd like to extend an invitation to use my
> servers: time.no-such-agency.net (stratum 1 GPS18 with a truetime server
> on the same lan as a backup time source) and skipjack.no-such-agency.net
> (stratum 2) to any pool server within 60ms RTT.
>
> John
> _______________________________________________
> timekeepers mailing list
> [email protected]
> https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
>
Thanks for the offer, but my time server (65.71.16.189) is consistantly
over 80ms away, I wish mine server was a little closer. My ISP is ATT
(formerly SBC) and they apparently have lousy time servers, they fail
and show as falsetickers all the time. Normally tick.UH.EDU is very
reliable for me.
ntpq -c pe
remote refid st t when poll reach delay offset jitter
==============================================================================
*ntp.okstate.edu .USNO. 1 u 89 128 377 81.507 -0.956 0.851
-time-B.timefreq .ACTS. 1 u 81 128 377 60.806 -3.580 1.654
tick.UH.EDU .INIT. 16 u - 1024 0 0.000 0.000 4000.00
+clock.xmission. .GPS. 1 u 83 128 377 66.130 -1.828 0.954
+time.nist.gov .ACTS. 1 u 17 128 377 61.126 -2.196 1.125
-father-time.t-b .GPS. 1 u 83 128 377 49.461 6.195 12.610
xntp1.sbcglobal. st1gs-ntp.rcsnt 2 u 25 128 377 23.163 -44.800 6.212
xntp2.sbcglobal. st1gs-ntp.rcsnt 2 u 22 128 157 26.451 -43.931 11.147
-ntp.tmc.edu time.nist.gov 2 u 21 128 377 28.539 3.894 5.654
-st1gs-ntp.rcsnt .GPS. 1 u 80 128 377 23.727 -42.780 0.725
Randy
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
