Metabase incident

Google SSO might not work in LATAM/other regions

Notice Resolved View vendor source →

Metabase experienced a notice incident on November 1, 2022 affecting Metabase Cloud Platform, lasting 7h 59m. The incident has been resolved; the full update timeline is below.

Started
Nov 01, 2022, 01:22 PM UTC
Resolved
Nov 01, 2022, 09:21 PM UTC
Duration
7h 59m
Detected by Pingoru
Nov 01, 2022, 01:22 PM UTC

Affected components

Metabase Cloud Platform

Update timeline

  1. identified Nov 01, 2022, 01:22 PM UTC

    On Oct-31th, Google pushed a change without notice to their oAuth2 flows to the LATAM and other regions changing the name of a parameter that broke all SSO flows. We're actively working to push a new version of Metabase with a hotfix along upgrading our Cloud instances. In the meantime, please use username/password authentication if you cannot authenticate to your Metabase instance.

  2. identified Nov 01, 2022, 07:40 PM UTC

    We finished the release process to obtain a new Metabase version that includes the fix for the issue. We'll be starting our Cloud upgrade process in the next hour.

  3. resolved Nov 01, 2022, 09:21 PM UTC

    We have started rolling out 44.6 version which includes the fix for the SSO issue. All instances should be upgraded in the next few hours.