Re: [time-nuts] Amazon AWS time sync service

2019-04-30 Thread Michael Shields via time-nuts
On Mon, Apr 29, 2019 at 5:00 PM Tim Shoppa wrote: > My reading is that Amazon does their smear for 24 hours before the leap > second, and Google does it for 10 hours before and 10 hours after. The smear Amazon uses is twelve hours before and after, i.e., smeared noon to noon. https://aws.amazon.c

Re: [time-nuts] Amazon AWS time sync service

2019-04-29 Thread Tim Shoppa
Long-term there is no drift to measure between regions. With each region on its own GPS receivers and atomic clocks, it seems much more likely that anything you measure will be asymmetries in network delays between regions. Note that like Google has since 2008, AWS "Time Sync" also smears out leap

Re: [time-nuts] Amazon AWS time sync service

2019-04-29 Thread Kevin Franzen
Subject: [time-nuts] Amazon AWS time sync service Hello Folks ! Some time ago Amazon AWS has introduced "Time Sync Service" https://aws.amazon.com/about-aws/whats-new/2017/11/introducing-the-amazon-time-sync-service/ Looks like it is just some NTPD (based on chrony). I am wandering how t

[time-nuts] Amazon AWS time sync service

2019-04-29 Thread Vlad
Hello Folks ! Some time ago Amazon AWS has introduced "Time Sync Service" https://aws.amazon.com/about-aws/whats-new/2017/11/introducing-the-amazon-time-sync-service/ Looks like it is just some NTPD (based on chrony). I am wandering how to measure drift between of AWS regions (internal clocks