airbyte_extract_date which time zone, is it from on premissi server?

Based on the knowledge sources, Airbyte stores and transports all timestamps in UTC, regardless of where your server is located (on-premises or cloud). Here's how time zones work across Airbyte's interfaces: • Backend/Storage: All timestamps are stored in UTC on the backend. [Time zones] • API, SDK, MCP: Timestamps are read and returned in UTC, formatted as ISO 8601 strings (e.g.,

2026-03-18T13:32:00Z

). [Time zones] • Web App Display: The web app formats timestamps in your browser's local time zone for display purposes only — the underlying value remains UTC. [Time zones] So fields like

_airbyte_emitted_at

and other Airbyte technical columns are in UTC, not in the time zone of your on-premises server. This is by design and is consistent regardless of where your source or destination server is located. > ⚠️ If you pass a timestamp into a connector action (e.g., as a date filter), you should use UTC. Any time zone conversion is your responsibility before passing the value to the platform. [Time zones] If you need data in a specific local time zone (e.g., Brussels time), you would need to handle that conversion on your end after the data is synced. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.