We’re seeing a pesky issue that arises after UTC midnight but before midnight EST where the dates shown in the relative date filter are correct yet the SQL executes a date range that is 1 day ahead.
For example, it is currently March 5th, 8:45pm EST and setting the date filter using relative date past 30 days excluding today shows Feb 3 – Mar 4, 2026. However, when I click into the query preview it says that it’s pulling BETWEEN date '2026-02-04' AND date '2026-03-05'.
I want to pull Feb 3- March 4th (matching current timezone) using the past 30 day relative date filter. I currently have the instance report time zone set to America/New_York and am using a fully hosted Metabase version. Are there any workarounds for this?
What database type are you running the query against, and what is the data type of the column you are applying the date filter to? And you have set the ‘report timezone’ in Metabase settings to America/New_York?
And just to clarify, “fully hosted” meaning self-hosted (running on your own server) or using a paid Metabase cloud plan?
We’re running this against a PostgreSQL DB, data type of the column is “date”, and we do have the report timezone in Metabase settings set to America/New_York.
Also, yes, I did mean to say self-hosted as opposed to a paid cloud plan
What is the database time zone set to?
The database time zone is UTC, but our ETL pipeline actually converts the dates in our key tables that Metabase is querying to PST so we’re expecting PST date boundaries ie:
(p.success_date AT TIME ZONE 'America/Los_Angeles')::DATE AS payment_date