How to write a time in an incident note
A practical format for tickets and chat: civil time, zone, and when an offset link is allowed as extra context.
Incidents
The stamp that survives next week
Use an ISO-like local time plus offset, or UTC. Example: 2026-09-02 14:05:12 +08:00. Example: 2026-09-02T06:05:12Z. Either can be sorted. “About two hours ago” cannot.
Get the civil time from /2-hours-ago if you truly do not have a log line. Then immediately rewrite it as a frozen stamp. Do not paste only the URL into the timeline.
One instant vs one question
An incident has one start instant. Everyone in the channel should see the same numbers. An offset link is a question against each reader’s clock. If you paste /2-hours-ago into Slack, a teammate in UTC-5 does not see your 14:05. They see two hours before their now.
Allowed: “Start 2026-09-02 14:05 +08:00 (I used /2-hours-ago to reconstruct; confirm against the dashboard).” Forbidden as the only record: “it started here: https://whattimewasit.app/2-hours-ago”.
Seconds
Deploys and failovers often sit less than a minute apart. Copy seconds from the result page. If two notes both say 14:05, you cannot order them. 14:05:12 and 14:05:47 you can.
Where the UTC grid helps
Under the main clock, each offset page lists the same instant in a strip of UTC offsets. Use that when you need to tell someone “that was 03:05 for you if you are on UTC-3”. It is still not a named zone. If they are in America/Chicago, write America/Chicago or UTC-5 / UTC-6 with the date, because Chicago moves.
Minimum useful incident line
Copy this shape. Fill from the calculator, then stop using the calculator as the record.
- Local
- 2026-09-02 14:05:12 Asia/Singapore
- Offset
- UTC+08:00
- UTC
- 2026-09-02 06:05:12Z
- Optional
- Reconstructed from /2-hours-ago at 16:05 local
Questions
Should the note use 12-hour time?
Prefer 24-hour or ISO. If a reader needs AM/PM, add it in parentheses after the 24-hour time, never instead of the date.