This may have been happening for a while now but I only noticed today. Is ROGERS blocking all NTP packets ? Because the primary NTP servers at National Research Council of Canada can no longer be queried for time data. These are public stratum 2 servers that have been available for well over 15 years but today no data flows ( or perhap in the last week? ) thus :
root@nix:~# ntpdate -B -v time.chu.nrc.ca 29 Aug 11:05:05 ntpdate: ntpdate firstname.lastname@example.org Fri Jul 22 17:30:52 UTC 2016 (1) 29 Aug 11:05:13 ntpdate: no server suitable for synchronization found root@nix:~# ntpdate -B -v 22.214.171.124 29 Aug 11:06:55 ntpdate: ntpdate email@example.com Fri Jul 22 17:30:52 UTC 2016 (1) 29 Aug 11:07:04 ntpdate: no server suitable for synchronization found
Thus the NTP service fails to bring in data and thus clocks are wrong by a very great deal. Forget milliseconds. We are talking minutes.
I wonder if another Dos attack is underway. You would probably be able to find out by calling them or sending an email. Here's a link to a May 4 2016 article on that very subject:
Well, its an idea but I highly doubt that would affect the stratum 2 NTP servers at University of Toronto which are blocked also.
Are you still having an issue? I tried looking into this and my cable modem was able to syncrhonize to both NTP hosts you mentionned:
root@cmprobe2:/etc # ntpdate -B -v time.chu.nrc.ca 8 Sep 14:23:20 ntpdate: ntpdate 4.2.8p8-a (1) 8 Sep 14:23:26 ntpdate: adjust time server 126.96.36.199 offset 0.008472 sec root@cmprobe2:/etc # ntpdate -B -v time.nrc.ca 8 Sep 14:23:34 ntpdate: ntpdate 4.2.8p8-a (1) 8 Sep 14:23:40 ntpdate: adjust time server 188.8.131.52 offset -0.001757 sec root@cmprobe2:/etc #