rewindex

CompaniesMetabaseIncidents

Metabase: Database incident

No impact listedStatus: resolvedStarted Resolved (-1552 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. resolved

    Around 16:30 PT we received a report of a customer that could not connect to it's Metabase instance. Our engineering team identified an issue on the application database which showed that the clusters weren't available in our cloud provider (CSP). After further investigation they found out that a cluster resize didn't apply correctly due to a configuration mismatch between the configuration scripts and the CSP offering resulting in downtime. The configuration script was modified to be compatible with the CSP and the database instances came back online.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Metabase, started 2021-06-10 21:21 UTC, resolved after -1552 min, 1 update(s).

Title
Database incident
Vendor
Metabase
Date
URL
https://rewindex.com/company/metabase/incidents/84p3zsj7mrtm

Metabase profileRecent Metabase incidentsAll outages on June 10, 2021Metabase in June 2021MarkdownJSON