#25234 [Bug]: Request Logs / Live Tail appear several hours behind when LiteLLM stores UTC values in timezone-naive SpendLogs timestamps
### What happened?
The LiteLLM UI `Request Logs` page appears several hours behind real-time even when `Live Tail` is enabled.
In my setup, activity that definitely occurred on `2026-04-06` shows up in the Usage dashboard, but the `Request Logs` page does not show those same recent requests yet. The logs page appears delayed by several hours.
I expected recent requests to appear immediately in `Request Logs` when `Live Tail` is enabled.
This looks like a timezone-handling bug in how LiteLLM stores or queries request log timestamps.
Observations: - LiteLLM config sets: ```yaml litellm_settings: request_timeout: 600 set_verbose: False json_logs: True timezone: "US/Central" ``` - LiteLLM container also has `TZ=US/Central` - Postgres container uses `TZ=America/Chicago` - Usage dashboard shows activity on `2026-04-06` - `Request Logs` / `Live Tail` does not show the same `2026-04-06` activity in real time
Database investigation suggests the root cause is: - `LiteLLM_SpendLogs.startTime` / `endTime` are stored as `timestamp without time zone` - recent rows are being written with UTC wall-clock values - the UI/log query path appears to treat them as local time …