Linked from

The 11 pages that link to Unix time, each with the reason it gives.

• Leap yearRelated: Calendar software converts its continuous count into dates that include February 29.

• Coordinated Universal TimeRelated: Many computer systems represent timestamps relative to an epoch rather than directly as UTC labels.

• Time zoneRelated: Computers often store instants independently of local zone display rules.

• ISO 8601Compared with: It encodes time as a numeric instant rather than a human-readable calendar string.

• Leap secondCompared with: Unlike UTC, Unix time does not have one universally implemented representation for the extra second.

• Network Time ProtocolRelated: Many NTP clients convert synchronized time into the Unix time used by operating systems.

• Calendar eraCompared with: It uses a numerical epoch for elapsed seconds rather than an era for calendar years.

• DayRelated: Software represents dates as elapsed seconds rather than counting calendar days directly.

• MidnightRelated: Its epoch is specified at midnight UTC, anchoring timestamps to a date boundary.

• Real-time clockRelated: Operating systems often translate the clock’s calendar reading into this timestamp representation.

• Year 2000 problemCompared with: It represents time differently and was not the source of the two-digit-year bug.