Epoch Time Guide

Where these numbers show up

Incident decks, webhook payloads, CSV exports, and database dumps all spew epoch timestamps. They’re just counters—seconds or milliseconds since 00:00:00 UTC on 1 Jan 1970. Machines love them because subtraction is trivial. Humans stare at 1709251200 and have no idea whether it maps to “right after deploy” or “last Thursday.”

That’s why bridges stall: one person pastes the number, someone else assumes milliseconds, another assumes seconds, and ten minutes vanish debating whether the spike was 03:01 or 30 years from now. Convert first or you’re storytelling, not debugging.

Examples you will actually use

Example: Log correlation during an incident

PagerDuty screams “burst at epoch 1771737600.” Drop it into the Epoch tool, leave the unit on seconds, and you instantly see 2026-03-24 00:00 UTC. Flip the output to America/Denver and paste “2026-03-23 18:00 MDT” into the war room so everyone aligns on the same moment. Copy the ISO string straight into the timeline—no more “what time was that again?” chatter.

Example: API payload sanity check

A webhook hands you "expires_at": 1774513200000. Those extra three digits shout milliseconds. Don’t divide in your head—switch the tool to “milliseconds” and see April 24, 2026 05:00 UTC instantly. Now the PM knows exactly when access ends, and you avoid the classic off-by-1000 unit bug.

Example: CSV exports

Finance dumps a column of 1708723200000-style values. Paste the list into batch mode, export ISO strings, and send back a readable sheet so nobody approves refunds using dates from 1975 by mistake.

Getting unstuck between epoch and ISO 8601

ISO strings like 2026-02-22T18:45:00Z read nicely until someone strips the Z or swaps in +02:00. Stop decoding by hand. Paste the string into the Epoch converter, set “ISO → Epoch,” and let it give you raw seconds. Once both timestamps live in epoch, subtraction ignores DST, locale, and whatever formatting sin the other team committed.

Need the reverse? Slam the epoch number into the tool, pick seconds or milliseconds, copy the ISO output, and dump it into Jira or Slack so stakeholders see a real date instead of numerology.

Best practices

• Keep the source of truth in UTC (epoch or ISO) and convert only at the edges for humans.
• Document whether each API, queue, or table emits seconds or milliseconds; guessing is how on-call shifts run long.
• When you share data, include both the epoch and ISO render so the next engineer doesn’t redo the conversion.
• Before blaming an integration, drop the timestamp into the Epoch tool and confirm the unit is what you expect.

FAQ

Do leap seconds break epoch time?

Not in practice. Unix time ignores leap seconds, so differences stay clean integers. Most OS vendors “smear” the extra second over a window instead of freezing the clock, which keeps your math steady.

What happens after 2038?

Old 32-bit systems overflow at 03:14:07 UTC on 19 January 2038. Anything modern uses 64-bit integers or doubles, but embedded boxes and ancient firmware may still need upgrades. Check them before they tick over.

Can I convert multiple timestamps at once?

Yes—batch them in the Epoch tool or script the conversion, then paste the readable output back into your ticket.