Why Every Timestamp Is Shown in Your Own Timezone

UTC is correct and useless at 3 AM

Most infrastructure tools default to UTC, and there's a good reason for it: it's unambiguous, it doesn't observe daylight saving, and every server on earth already agrees what time it is. All of that is true and none of it helps the person reading an alert half-asleep, trying to work out whether "02:47 UTC" means something happened five minutes ago or five hours ago.

What this means in practice

Every timestamp you see — in the dashboard, in an incident's start and recovery time, in the subject line of an alert email — is converted to the timezone on your account, not left in UTC for you to convert yourself. An alert reads "went down at 2:20 AM", in your 2:20 AM, not a number you have to run through a converter before you know if it's worth getting out of bed for.

Built India-first

This product was built with Indian small businesses and site owners as the default case, not an afterthought localization pass. IST is the timezone new accounts default to, and every part of the product — the dashboard clock, the alert emails, the incident log — was designed around actually being read at 2 AM IST, not adapted after the fact from a UTC-first version.

The setting lives on your account, not per-monitor

Timezone is a property of you, not of an individual site — nobody wants to remember that one monitor shows times differently from the rest of the dashboard. Change it once in Settings, and every timestamp everywhere follows.