Hi Ross:

> One other oddity about the logs: most of the GET times seem to be UTC,
> but some of them are local time (US/Pacific, currently -0700).

Yup I realized there's a pattern there. If the URL is inside the tracker, the UTC timezone
is printed. If the URL is outside the tracker you get the system timezone: US/Pacific.

This is inside tracker '/demo/' and timezone is set in config.ini
with the [main] timezone setting to UTC or 0:
> 127.0.0.1 - - [23/May/2026 02:07:10] "GET /demo/rest HTTP/1.1" 403 -

This is outside the tracker, so using system timezone.
> 127.0.0.1 - - [22/May/2026 19:07:10] "GET /favicon.ico HTTP/1.1" 200 -

Inside:
> 127.0.0.1 - - [23/May/2026 02:07:42] "GET /demo/index HTTP/1.1" 200 -
> 127.0.0.1 - - [23/May/2026 02:07:42] "GET /demo/rest HTTP/1.1" 403 -

Outside:
> 127.0.0.1 - - [22/May/2026 19:08:57] "GET / HTTP/1.1" 302 -

Inside:
> 127.0.0.1 - - [23/May/2026 02:08:57] "GET /demo/index HTTP/1.1" 200 -

Roundup server can serve multiple trackers with only one server. So you could
have one tracker for the German office in the Europe/Berlin timezone by default
and one for the New York office in America/Eastern. Both can be served by
the same roundup-server. Each user of the tracker can also set their own timezone
offset. So a user in California can see times in the German tracker in their local
US/Pacific time.

So what you observed makes perfect sense. What to do about it, if anything,
is less obvious. There are a number of ways to server roundup some of which
generate their own logs that are independent of Python logging.
I opened issue 2551418 to track/discuss.