Is Hipchat Server affected by Leap Second?

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

A leap second is a one-second adjustment that is occasionally applied to UTC (Coordinated Universal Time) in order to keep its time of day close to the mean solar time. The most recent leap second insertion happened on June 30, 2012 at 23:59:60 and caused disruptions in computing systems all around the world.

Resolution

Hipchat Server runs an NTP (Network Time Protocol) service that is resilient to leap second. As such, no action is required at the user or administrator level to prevent Hipchat Server from being affected by problems related to leap second.

Last modified on Jan 19, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.