Skip to main content
Metabase Cloud

Google SSO might not work in LATAM/other regions

Degraded Lasted 8h · started · Metabase Cloud's page

Level
confirmed
Worst impact
Degraded
Components
Metabase Cloud Platform
Regions
latam

What to do

  • Check whether you use Metabase Cloud Metabase Cloud Platform in latam. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 8h it lasted.

    Anything that failed between 2022-11-01 13:22 UTC and 2022-11-01 21:21 UTC may need a replay.
  • Subscribe to Metabase Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=metabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Metabase Cloud 3

  1. identified

    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.

    provider

  2. identified

    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.

    provider

  3. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-69ba6145c1

Is Metabase Cloud still down?

No, this incident was resolved 2022-11-01 21:21 UTC. For Metabase Cloud's live state, see https://down.guide/metabase.

How long did it last?

8h, from 2022-11-01 13:22 UTC to 2022-11-01 21:21 UTC, by the times Metabase Cloud posted.

What was affected?

Metabase Cloud named Metabase Cloud Platform in latam.

What caused it?

Metabase Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Metabase Cloud's official status page, https://status.metabase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.