Ask Bjørn Hansen wrote:
>
> Looks okay from here ....
>
> http://www.pool.ntp.org/scores/218.21.130.42
>
It has several good timesources but it seems to be behind a ~200ms delay
last hop.
ntpq -p 218.21.130.42
remote refid st t when poll reach delay offset
jitter
==============================================================================
+time.nist.gov .ACTS. 1 u 1856 1024 342 263.928 -4.873
2.191
-clock.isc.org 204.123.2.5 2 u 855 1024 377 223.930 9.000
0.661
*clock.via.net .GPS. 1 u 1650 1024 376 209.977 2.941
0.329
-cpe-76-168-23-8 .GPS. 1 u 891 1024 377 225.765 -8.547
7.173
+cpe-76-169-239- .GPS. 1 u 30 1024 377 240.736 -3.256
0.061
-cpe-76-169-237- .GPS. 1 u 928 1024 377 232.938 7.196
3.041
-time-nw.nist.go .ACTS. 1 u 878 1024 231 224.747 7.826
0.611
-clock.fmt.he.ne 10.200.208.2 2 u 829 1024 377 209.563 6.329
0.258
+avi-lis.gw.ligh .CDMA. 1 u 979 1024 377 292.396 1.247
0.689
Should work OK when used as an ntpd reference, but I could imagine
trouble when some SNTP client is used...
Rob
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
