Y2K date rollover (1999-2000)
As the calendar turned to 2000, computer systems worldwide were scheduled to evaluate dates written with two-digit years. Companies and governments spent years auditing code and running tests, because a shared clock would make many independent systems act at once.
Few serious failures materialized, and the rollover passed with scattered, limited disruptions.
The episode made clear how much infrastructure depends on synchronized time, and it established practices for testing clock-driven software before a deadline.
Both cases turn on the same mechanism: a shared clock causing many separate machines to act simultaneously, with consequences that only appear at the system level.
