---
title: Timezone errors in self-hosted Langfuse
description: "Missing traces or observations on self-hosted Langfuse are often a timezone mismatch. Verify that both databases run in UTC."
tags: [self-hosting]
---

# Timezone errors in self-hosted Langfuse

**Langfuse requires all infrastructure components (ClickHouse and Postgres) to run in the UTC timezone.** Non-UTC timezones are not supported and will cause queries to return incorrect or empty results.

If you are seeing missing traces or observations, verify that both databases are running in UTC.

## Postgres

Check the effective timezone for the Postgres connection:

```sql
SHOW timezone;
```

This should return `UTC`. If it returns a different timezone, set the [`timezone`](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TIMEZONE) parameter to `UTC` for the Postgres connections used by Langfuse, then restart Langfuse so that it opens new database connections.

## ClickHouse

Check the ClickHouse server timezone:

```sql
SELECT timezone()
```

This should return `UTC`. If it returns a different timezone, update your ClickHouse server configuration to remove any custom [`timezone`](https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#timezone) setting and restart the server.

If you would like us to consider supporting other timezones, please vote on this [GitHub Discussion](https://github.com/orgs/langfuse/discussions/5046).

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/self-hosting-timezone-errors.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.