An incident timeline orders observations from different sources. Use a common time zone and keep the original timestamp visible in your records. A sequence gives you a way to ask what may be related.
Incident Response · Lesson 3
Incident Timelines
Learn to place evidence on one timeline while marking uncertain event times.
Converting One Timestamp
Here a web report uses UTC and a deployment record uses an offset of two hours ahead of UTC.
Deployment record: 2026-11-19 11:17:00 +02:00
Web report: 2026-11-19 09:22:00 UTC
On a Linux system with GNU date, -d reads a supplied timestamp and -u requests UTC output. The argument beginning with + sets the display format.
$ date -u -d '2026-11-19 11:17:00+02:00' '+%Y-%m-%d %H:%M:%S UTC'
The result is 2026-11-19 09:17:00 UTC. In this example it precedes the web report by five minutes.
Which entry occurred earlier in the normalized timeline?

Distinguishing Observations from Estimates
A report can state that the first failure occurred around 09:19. Keep that as an estimate. A user's report time is separate from the actual first failed request. Mark each row with its source and time precision.
A teammate says around 09:19. How should that appear?
Ordering Without Assigning Cause
A deployment can precede a service problem without being its cause. Check whether the affected route changed and whether other signals support the connection. Keep open questions visible beside the timeline.
What does the ordered sequence establish by itself?
Lesson complete
You finished Incident Timelines
You can now build a timeline that keeps evidence and uncertainty visible.
Convert recorded time zones consistently.
Attribute each time and mark estimates.
Use the sequence to choose follow-up checks.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account