Adding leap second this year expected to cause Internet problems

clock
Credit: Vera Kratochvil/public domain
(Phys.org) —Officials at the International Earth Rotation Service have announced that a leap second will be added to the year this summer to allow for syncing up atomic clock time with the Earth's rotational time. The announcement has made many Internet sites nervous, as adding leap seconds in the past has caused problems with services such as Foursquare, Reddit, Linkedln and Yelp—all reported incidents due to the sudden time discrepancy the last time a leap second was added back in 2012.

The advent of computers and the Internet has caused a need for ever more precise measurement and scientists have responded—atomic clocks are the standard now with accuracy up to quadrillionths of a second. Unfortunately, the spin of the Earth on its axis, which of course is the for recording the passage of time—one spin equals one day—is slowing down, losing approximately two thousandths of a second every day. That means that atomic clocks and true Earth time must be reconciled every so often—it has happened 25 times since it became necessary back in 1975. But back then, adding leap seconds went virtually unnoticed by all but the most interested. Nowadays, however, adding a leap second—which is scheduled to occur at 23:59:59 on June 30 (the halfway point of the year)—can cause computer systems to become confused when their clock shows 60 seconds, rather than rolling over after 59—and we all know what that generally means—outages. Other computers will show the 59th second for two seconds in a row, which can also cause problems.

Some companies, most notably, Google, have created a work-around—they call it the "smear around"—it forces servers to use extra time in making updates over the course of the year, which prevents them from ever noticing that a leap second has occurred. That approach apparently worked well enough as Google has already announced that it would use the same technique this year. Whether other sites will be doing the same is still not clear.

Because of such disruptions, some in the technology sector have called for an end to leap seconds—doing away with time based on the Earth's movement altogether. That would not mean much of a difference in the near term, but at some point, people would find their clocks completely mismatched with days and nights, perhaps necessitating the need for a leap minute, or hour which would seem to be even more disruptive. Another possibility is of course, to maintain a dual system, one for technologists, the other for everybody else.


Explore further

Leap second to be added

More information: International Earth Rotation Service: www.iers.org/IERS/EN/Home/home_node.html

© 2015 Phys.org

Citation: Adding leap second this year expected to cause Internet problems (2015, January 7) retrieved 26 May 2019 from https://phys.org/news/2015-01-adding-year-internet-problems.html
This document is subject to copyright. Apart from any fair dealing for the purpose of private study or research, no part may be reproduced without the written permission. The content is provided for information purposes only.
3444 shares

Feedback to editors

User comments

Jan 07, 2015
Because of such disruptions, some in the technology sector have called for an end to leap seconds

Only solution: We need to speed up the earth rotation.
Seriously: if the sites are afraid of problems then they should just take themselves offline for a minute. It's not like that would be the end of the world.

Jan 07, 2015
Lack of foresight; just like the Y2K bug. The only real solution is to account for it in system design and in less than 5 years, as sensible services need to adjust to the rapidly changing technology, it would be fixed. We seriously need to deal with the UNIX (POSIX timestamp) leap second handling mess. A second is a second and is well define in the SI system; smudging it is not the solution.

Jan 07, 2015
I wonder if it would be easier for everything to just use universal time (UT). Or at least use UT for computers

Jan 07, 2015
Is there some way I can tell my computer to ignore the extra leaping second and just let my interweb be a second late all the time? Maybe the scientist-Skippys need the leaping second but it really is not that important to me because if everything is within two minutes I'm good.

Jan 07, 2015
If everybody who isn't an anal-retentive dweeb just left everything alone then nobody would give a rat's behind.

Of course, you'd have the exchange trolls going, "..but do you know how much money is lost and earned in a single second?!!"

..tell it to the hand

Jan 08, 2015
Ahhh... I remember the Y2K debacle.... I made SOOO much money doing upgrades.... (that weren't all that necessary)...

Jan 08, 2015
Lack of foresight;

C'mon - when you develop software thinking about the particulars of the Earth's rotation and how that could play into your software every few years is not exactly at the forefront of your mind.

Jan 08, 2015
Internally, all major operating systems maintain time as a simple count of seconds since some epoch, or start time. They care not a bit about when the sun rises and sets, or if a day is exactly 86400 seconds long. Well designed application software would internally use time values the same way. Alas, that's not how things seem to be done in the real world.

Those of us cursed to live in a daylight savings time zone have to deal with this sort of discontinuity twice a year.

Jan 09, 2015
The problem is that the leap second is applied to UT, so what time zone your computer is in doesn't matter.


@nkalanaga yes you are right, good point, what I said sounded good to me at the time but I guess I didn't think it through lol

Jan 10, 2015
nkalanaga: that page and this one seem to have totally incongruent data..
this page says
"losing approximately two thousandths of a second every day."
that page says
"with days lengthening by 1.7 milliseconds per century."

those are about 5000000% different.
if we've had to do it recently, I'd believe the first..

and null has a good point in that any good system will be operating on an absolute tick system(seconds since midnight jan 1 1970 is the 'timestamp' for most computers) . the problem is that if you calculate that straight with only using leap days, Youre interpretation of the time will be off by a few seconds which can be a very big problem for GPS devices and things that need to be synchronized
the way this will work out is that they'll release a new 'base numeral'. so, if 12:59:59 jun 30 is 1500000 (it's not..) then the 'update' would say 1500002 = 1:00:00 and any time after that can be calculated with the basic system.

Jan 10, 2015
Wandering Gyre
Y2K certification was the easy money. Scan the code for any date handling routines, check the underlying datatype and manipulation and then produce a report stating whether it was at risk or not. If deemed at risk a quote to undertake mitigation could be supplied, for a fee.

A full blown investigation of a large system including all internal and external data sources/sinks was guaranteed serious cash in the bank. You did have to know what you were doing not just pull a recommendation out of your @rse but it really wasn't that hard and paid very very well indeed.

Jan 11, 2015
@lamval
nkalanaga: that page and this one seem to have totally incongruent data..
this page says
"losing approximately two thousandths of a second every day."
that page says
"with days lengthening by 1.7 milliseconds per century."

It just means that now the days are too long by .002 seconds and in one century it will be too long by around .0037 second. Just don't take my words for it, follow my link and read the paragraph named: Did you know... http://www.timean...und.html

Jan 12, 2015
The days are just fine. Your clocks are wrong.

Please sign in to add a comment. Registration is free, and takes less than a minute. Read more