Re:Did iOS 9 set millions of iPhone clocks to the wrong time?
by toufka on Tuesday September 22, 2015 @11:50PM
(#10263229)
It affects (non-cellular) iPads with iOS9 as well, so likely not a carrier-related issue. So it's not issue #3. And like you say, a lot more than iOS9 would be out of sync if it was #2. So we're going to have to go with #1 - Apple broke something in ntp.
Re:Did iOS 9 set millions of iPhone clocks to the wrong time?
by waz0wski on Tuesday September 29, 2015 @05:39PM
(#10299884)
wonder if it's due to something that's changed as part of the battery life improvements, from process scheduling to clockspeed changes
Re:Did iOS 9 set millions of iPhone clocks to the wrong time?
by jameswilsterman on Tuesday September 22, 2015 @10:57PM
(#10263097)
For me the problem seems to affect both WiFi and LTE (on Verizon).
What's crazy is that my clock seems to be getting worse. It's gone from 5s off to now ~20s off since I've upgraded.
It's simple ntp. The computers ask DNS for time.apple.com, while the iOS devices ask for a similar domain, time-ios.apple.com. From that point both types of devices make ntp requests. What I do on my firewall is redirect those requests to my local ntp server, this saves on external ntp traffic.
time.apple.com resolves to 12 different IP addresses, all on Apple's 17.0.0.0/8 network. It's easy to see, just issue the following command and you'll see all of them:
These servers are pretty darn good, they're stratum 1, they're distributed all over the world. Time from them seems to agree to within milliseconds of each other. The iOS address only seems to resolve to 3 places, but those also agree to milliseconds of each other.Given that, I can think of at least 3 different error scenarios:
1) Apple broke something in actual ntp implementation in iOS 9.
2) One of the iOS ntp servers is goofing up. Unlikely since I'm sure Apple doubtlessly has lots of monitoring for errors like that.
3) Without WiFi available, iOS relies on the cell carrier for time services. Of course, the operation of the cell network depends on all phones knowing the exact time, but that probably doesn't carry over to something ancillary like ntp. Perhaps a carrier's ntp server is borked?
To resolve this it would be interesting to know and try:
Why would anyone update to 9.0.0 anyway? New software always has teething problems.