---
title: Every dashboard timestamp follows your profile time zone and clock
description: The same incident could read 10:30 on the incidents list and 13:30 on the monitor's Incidents tab, because parts of the dashboard were still using your…
canonical: https://watchfor.io/changelog/2026-09-06-dashboard-time-zone
---

[All updates](/changelog/page/4#2026-09-06-dashboard-time-zone) 🐛 Fixed Sep 6, 2026 · v 6.8.1

# Every dashboard timestamp follows your profile time zone and clock

The same incident could read 10:30 on the incidents list and 13:30 on the monitor's Incidents tab, because parts of the dashboard were still using your browser's time zone instead of the one in your profile. That was our bug, and it made comparing an incident with your own logs unnecessarily hard. Incident pages, the incidents list, the Probes tab and the notification delivery log now all use your profile time zone and 12/24-hour setting (avatar → Settings → Profile); the incident header keeps the offset next to the start time so there is never any doubt.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-06-dashboard-time-zone · Site guide: https://watchfor.io/llms.txt
