Epoch and unit confusion

Seconds vs milliseconds vs microseconds, and non-Unix epochs (NTP 1900, Apple 2001, Windows FILETIME 1601), place events off by 1000× or in the wrong century — a whole dataset lands in one slot or in 1970.

Class

Case to account for

Affects

1 conversion

Detection

Implausible resolved year (1970 clustering, 1601, or far future).

Mitigation

Assert the unit and epoch on ingest; range-check to a plausible window.

Affected conversions

Timestamp + zonehour-of-week slot

OPEN