Provider
MetabaseIncident detail
Google SSO might not work in LATAM/other regions
Timeline window
to
Get alerted the next time Metabase breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
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.
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.
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.
Keep exploring
More from Metabase
Neighboring incidents on Metabase's timeline and the rest of their record on OutageDeck.