Keep a converter open during every incident
Paste raw epoch values into the Epoch converter to see UTC, your local time, and ISO strings side by side. The tool also lets you go the other direction: type a human time and copy the epoch for API calls. Keeping it open prevents arithmetic mistakes when adrenaline is high.
Example: API outage timeline
Logs show an error spike at 1778013600. Drop it into Epoch and note it maps to 2026-05-12 14:00 UTC / 07:00 PT. Another service logs recovery at 1778015400 (14:30 UTC). Share those readable times in the incident doc so engineering and customer success can align on what customers saw.
Example: Mobile push drift
Your analytics pipeline emits events at 1779552000 while customer screenshots show 2026-06-01 09:00 London. Converting 1779552000 reveals 08:00 UTC, meaning London devices were one hour ahead because British Summer Time was active. Pair the converted timestamp with the DST Planner to confirm future drift windows.
Checklist for log reviews
- Copy raw epoch values into Epoch before sharing timelines.
- Record both UTC and stakeholder-local timestamps in your notes.
- Note whether DST was in effect when the event happened.
- Store the converted timestamp next to the log line for future audits.
Try the tools
Related guides
FAQ
- What precision does the converter support?
- Seconds and milliseconds. Paste the number as-is and the tool handles the rest.
- Do I need to know the timezone of the log server?
- No. Epoch timestamps are absolute. The converter shows multiple timezones so you can narrate the event for any audience.
- How do I compare two timestamps quickly?
- Convert each, then feed the human-readable dates into the Date Difference tool for gap analysis.
Need another conversion mid-incident? Keep the Epoch converter open.