Dear colleagues, Last month we covered the 2015 leap second ahead of the insertion of a leap second at the very end of 2016. As stated previously, leap seconds can trigger poorly-tested code paths; leap second handling always unearths bugs and issues. This one was no exception!
Please find more details on RIPE Labs: https://labs.ripe.net/Members/stephen_strowes/reviewing-the-2016-leap-second Kind regards, Mirjam Kuehne RIPE NCC
