---
title: "Discussion on \"Why Time Is Hard in Distributed Systems?\" | Hashnode"
description: "Discussion on \"Why Time Is Hard in Distributed Systems?\". In 2012, a leap second was added to UTC at midnight. Within hours, servers running Linux at Reddit, LinkedIn, Yelp, and several other companies started spiking CPU usage to 100% and locking up. Engine"
url: "https://hashnode.com/posts/why-time-is-hard-in-distributed-systems/6a524d00c998ce2ea8041508"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Time Is Hard in Distributed Systems?](https://backend-bytes.hashnode.dev/why-time-is-hard-in-distributed-systems?utm_source=hashnode&utm_medium=feed)

In 2012, a leap second was added to UTC at midnight. Within hours, servers running Linux at Reddit, LinkedIn, Yelp, and several other companies started spiking CPU usage to 100% and locking up. Engine

Jul 11 · 6 min read · backend-bytes.hashnode.dev  
Read the article

-   [#distributed-systems](https://hashnode.com/tag/distributed-systems)
-   [#backend-development](https://hashnode.com/tag/backend-development)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#time](https://hashnode.com/tag/time)

## Written by

[Devesh Parmar](https://hashnode.com/@deveshparmar)

@deveshparmar · Ahmedabad, Gujarat

  
[View profile](https://hashnode.com/@deveshparmar)

SDE @ Ei

Software Development Engineer ~ System Design, AI, Finance, Tech

## Responses

Markdown supported · ⌘↵ to post

No responses yet.