About this tool
Incident timelines often cross midnight, shift boundaries and maintenance windows, which makes manual duration calculations easy to get wrong. This tool calculates elapsed time between two timestamps.
Use it for outage bridges, RFO preparation, SLA evidence, shift handoffs and ticket reviews where a precise duration is needed.
How to use it
- Enter the incident start timestamp.
- Enter the incident end timestamp.
- Calculate and copy the elapsed result into your ticket or report, using the same timezone for both values.
Example: 22:35 to 01:20 the next day
The elapsed time is 2 hours and 45 minutes. Crossing midnight does not change the calculation as long as the dates are entered correctly.
Engineering notes
- Be explicit about timezone when teams work across regions. “02:00” is ambiguous without a zone during distributed incidents.
- For SLA reporting, distinguish service-restored time from ticket-closed time if the ticket remains open for validation or documentation.
Frequently asked questions
Does the calculator account for dates as well as times?
Yes. Use full start and end date/time values.
What if the end time is earlier than the start time?
That indicates an invalid range unless the dates make the end occur later. Correct the timestamps before using the result.
Should bridge-start time be the incident start?
Not automatically. Use the start point defined by your operational metric or SLA, such as first customer impact or monitoring detection.