A timestamp records a point in time, often including a date and a clock value. It becomes much more useful when the time zone or offset is known. Support logs, payments and viewing incidents may use different clocks, so a precise report should connect the observed local time with the relevant date and zone for comparison.
A practical example
A viewer reports a failure at 21:15 local time and includes the country or named time zone. Support can then compare it with server events stored in UTC rather than assuming both records use the same clock reading automatically.
A common misunderstanding
A bare time such as nine o'clock is ambiguous across dates and zones. Include enough context to distinguish repeated events, travel, seasonal clock changes and logs produced by another system.
Related terms
General operational definition; actual service terms remain separate. Editorial approach