Canada's November 1 time-zone change leaves Cloud SQL and Looker an hour behind

On November 1, 2026 at 02:00 local time, affected areas of British Columbia, Alberta, Manitoba and the Northwest Territories retain their summer UTC offsets instead of falling back an hour. Google's October 30 Cloud SQL for SQL Server release notes warn instances evaluating affected local Canadian zones will lag by an hour because their time-zone rules still apply the old fall-back. Google recommends changing affected instance time-zone settings to interim fixed-offset Windows zone identifiers. Microsoft's October 14 SQL guidance provides the same mappings and explains when SQL Server and Azure SQL need a Windows or runtime update. Google separately warns Looker scheduler, browser and JVM components can evaluate affected zones incorrectly until patched, and that some server-side calculations remain wrong even after a supported Looker patch.

A one-hour local-time discrepancy can misfire scheduled jobs, reporting, billing windows, dashboards, application notifications and audit timelines. The stored database timestamp values do not change, but interpreting them using obsolete regional rules does. Operators need to identify affected jurisdictions, verify the time-zone data of every runtime and database, and apply product-specific patches or carefully scoped workarounds without accidentally changing historical winter conversions.

Affected areas include most of British Columbia (UTC−07:00), Alberta and affected Northwest Territories locations including Inuvik (UTC−06:00), and Manitoba (UTC−05:00). Some bordering jurisdictions and exceptions require local checks; do not apply one province-wide workaround to every BC or NWT location. The changes take effect November 1 at 02:00 local time, when old software would incorrectly fall back.

Google's October 30 release note explicitly says instances that evaluate affected local Canadian zones will lag by one hour. It recommends mapping Pacific Standard Time to Yukon Standard Time for affected BC, Mountain Standard Time to Canada Central Standard Time for affected Alberta/Inuvik, and Central Standard Time to Eastern Standard Time (Mexico) for affected Manitoba. These are temporary matching-offset identifiers; operators can update instance time zones in the Cloud Console or with gcloud. Stored timestamp data is not modified.

Microsoft says SQL Server on Windows needs the applicable Windows time-zone update rather than a separate SQL Server product patch. For SQL Server on Linux, Azure SQL Database and eligible Managed Instance configurations where new regional zones are not yet available, it publishes interim fixed-offset identifiers. Existing Azure SQL Managed Instance instance-level time-zone settings cannot be changed, so mitigation may require query or session-level handling. Microsoft cautions that new region-specific zone identifiers and patches have different availability across products.

Google's Looker guidance says patched builds can update scheduler Ruby time-zone data and browser-side JavaScript calculations, but bundled JVM tzdb in some Looker-hosted/core instances remains old and server-evaluated now() can still be one hour off. Google says Looker patches will not be automatically deployed to all instances before November 1; hosted users may need support, while customer-hosted installations can update their runtime's time-zone database. Scheduled delivery time-zone workarounds differ from query-level changes.

Using a permanent fixed-offset replacement may fix today's local clock but shift historical winter data because older dates legitimately observed different offsets. Google explicitly warns against broadly changing Looker query-level time-zone settings unless historical changes are understood. Test representative historical and future timestamps, scheduled delivery triggers, audit displays and billing periods before deploying a workaround.

Identify databases, BI tools, Java, PHP, Node.js and scheduled jobs using affected IANA or Windows time-zone identifiers. Confirm whether the runtime has tzdata 2026e or an equivalent vendor fix. Test November 1 and earlier winter timestamps. For Cloud SQL, follow Google's precise region-to-zone table. For Looker, distinguish scheduler, browser and server JVM evaluation; request patched builds where applicable. Monitor scheduled runs and customer-facing timestamps around the transition.