When system clocks drift by just a few hundred milliseconds, catastrophic distributed failures begin: 1. Distributed Consensus Split-Brains: Raft clusters (etcd, Consul, Patroni) rely on precise election timeouts. Clock skew can cause healthy nodes to believe the leader has timed out, triggering non-stop leader elections and cluster paralysis. 2. Kerberos & Auth Ticket Rejections: Kerberos protocols strictly enforce a 5-minute clock skew window. A drifted node suddenly rejects valid authentication tokens, locking engineers and services out of production. 3. Cryptographic Invalidation: TLS certificates evaluated against a skewed system clock appear expired or "not yet valid," breaking API handshakes without warning. 4. Transaction Sequencing Corruption: Database engines relying on timestamps for conflict resolution or multi-version concurrency control (MVCC) silently overwrite newer data with older records.