Time zones.
How Vericto stores timestamps in UTC, converts them to your time zone in the dashboard, and what that means for the time selector, audit trail, and exports.
Overview
Every event Vericto records — intercepted queries, blocks, triggered rules — is stored with a UTC timestamp. The dashboard converts them to your preferred time zone for display, but the source of truth is always UTC.
This ensures data is consistent regardless of where you or your team are located, and avoids ambiguity during daylight saving time transitions.
General rule: everything is stored in UTC, everything is displayed in your time zone. CSV/JSON exports include timestamps in ISO 8601 with the UTC offset (2026-07-01T14:30:00.000Z) so any tool can interpret them correctly.
How it works
1. Storage: always UTC
The TCP proxy records the timestamp of each query at evaluation time, using the server clock in UTC. This value is never modified when stored in the Vericto database.
# Ejemplo de timestamp almacenado
event.created_at = "2026-07-01T19:30:00.000Z" # UTC siempre
2. Display: your preferred time zone
When you open the dashboard, Vericto automatically detects your browser time zone (Intl.DateTimeFormat().resolvedOptions().timeZone). You can pin a different time zone in Settings → Account → Time zone, and that preference syncs to your account for consistency across all your devices.
The time selector shows the active zone in its footer: for example GMT-5 (UTC-5). The range shown in the timeframe field — such as 07/01/2026, 14:30 AM → 07/01/2026, 02:30 PM — is expressed in your local time zone, even though queries use UTC internally.
The time selector
The Overview time selector appears in the top bar of the dashboard. Here is how it works:
| Element | Description |
|---|---|
| Timeframe field | Shows the active range in a readable format, expressed in your local time zone. Read-only for presets; editable when choosing a custom range. |
| Calendar icon | Opens two datetime-local fields to choose an exact range (start and end). Values are interpreted in your local time zone and converted to UTC internally. |
| Apply button | Confirms the custom range and triggers a new backend request with from_date and to_date parameters in UTC. |
| Presets | Shortcuts relative to the current moment (-1h → Now, -24h → Now, etc.). The backend always resolves them from the request instant in UTC. |
| Recently used | The last 3 presets or custom ranges you used, for quick access. |
| Time zone footer | Shows your active zone (e.g. GMT-5 (UTC-5)). Click "Learn more" to reach this page. To change it, go to Settings → Account. |
Custom range and time zones
When you enter a custom range using the calendar, the values you type in the inputs are interpreted as your local time. For example, if your zone is America/Bogota (UTC-5) and you type 2026-07-01T09:00, Vericto converts it to 2026-07-01T14:00:00Z (UTC+0) before sending it to the backend.
# Lo que ves en el input (hora local America/Bogota, UTC-5)
From: 2026-07-01T09:00
To: 2026-07-01T17:00
# Lo que Vericto envía al backend (UTC)
from_date: 2026-07-01T14:00:00.000Z
to_date: 2026-07-01T22:00:00.000Z
Changing your time zone
There are two ways to adjust the time zone Vericto uses to display data:
Automatic (recommended)
Leave the setting on Automatic in Settings → Account → Time zone. Vericto uses the browser's zone (Intl.DateTimeFormat().resolvedOptions().timeZone) each session. If you travel or switch devices, the display adapts automatically.
Fixed (ideal for distributed teams)
If your team works from multiple countries and you want everyone to see the same times in reports, pin an explicit time zone to your account:
- Go to Dashboard → Settings → Account.
- In the Display preferences section, select the zone in the time zone picker.
- Save. The preference syncs to your account and applies on all devices where you log in.
Changing the zone does not reinterpret historical data. It only changes how UTC timestamps are displayed. An event recorded at 14:00 UTC will appear as 09:00 in UTC-5 or 16:00 in UTC+2 — same instant, different representation.
Audit trail and exports
The Audit Trail page filters events by time window using the same logic as the Overview: date inputs you type are interpreted in your local zone and converted to UTC for the query.
CSV/JSON exports
Exported files contain timestamps in ISO 8601 with UTC offset (Z). This ensures any analysis tool — Excel, Python, dbt, BigQuery — interprets them without ambiguity:
# Columna timestamp en un export CSV
event_id,timestamp,status,rule_code,latency_ms
b4f2...,2026-07-01T14:30:00.000Z,BLOCKED,VERICTO-001,1.8
c9a1...,2026-07-01T14:30:01.123Z,ALLOWED,,0.9
If you need timestamps in your local zone for analysis, convert them in your target tool. Python example:
import pandas as pd
df = pd.read_csv('audit_export.csv')
df['timestamp'] = pd.to_datetime(df['timestamp'], utc=True)
# Convertir a tu zona local
df['timestamp_local'] = df['timestamp'].dt.tz_convert('America/Bogota')
Daylight saving time (DST)
By storing everything in UTC, Vericto is immune to daylight saving time changes. An event that occurs right at the clock transition has a unique, unambiguous UTC timestamp.
Conversion to local time applies the correct offset for each historical instant using IANA rules. For example, in America/New_York:
| UTC timestamp | Local time (NYC) | Offset |
|---|---|---|
2026-03-08T06:59:00Z | 01:59 AM EST | UTC-5 |
2026-03-08T07:00:00Z | 03:00 AM EDT | UTC-4 |
2026-11-01T05:59:00Z | 01:59 AM EDT | UTC-4 |
2026-11-01T06:00:00Z | 01:00 AM EST | UTC-5 |
The dashboard automatically applies the correct offset for each instant. No additional configuration is needed.
Frequently asked questions
Why does the selector show a different time than the log on my server?
Your server likely uses local time while Vericto uses UTC. Compare timestamps by adding or subtracting your UTC offset. For example, if you are in UTC-5 and Vericto shows 14:30 UTC, your local server would show 09:30.
Can I filter the audit trail by local time?
Yes. Date inputs in the audit trail and Overview time selector accept dates in your local time zone. Enter the time you see on your clock and Vericto converts the search to UTC internally.
Does the time zone affect Slack/webhook notifications?
Notification messages include the event timestamp. By default, Vericto formats them in UTC. A future version will add the option to customize the date/time format in notifications.
What happens if I change my time zone while a session is open?
The change takes effect on the next navigation click or data refresh. No need to log out.