rewindex

CompaniesMetabase CloudIncidents

Metabase Cloud: Problems when creating instances

MinorStatus: resolvedStarted Resolved (3.3 h)2 updatesstspg.io (opens in new tab)
Part of an outage event

AWS outage, Jun 13, 2023 · 29 vendors, 32 incidents

Metabase Cloud’s incident blames AWS as the cause. (hop 1, posted +44 min vs the first vendor naming AWS)

“…Problems when creating instances AWS reports that the service should be normalized now AWS reports that the service should be normalized now There is a problem with our cloud service provider that doe…”

Swipe sideways to see the whole diagram.

depends on AWSAWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, Temporal Cloud, Ashby +91 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana, JFrog +3Known dependency9 vendorsUnbounce, Mapbox, Klaviyo, Webflow +5Metabase Cloud (this incident)posted +44 min
depends on AWSAWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, TemporalCloud, Ashby +91 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana,JFrog +3Known dependency9 vendorsUnbounce, Mapbox, Klaviyo,Webflow +5Metabase Cloud (this incident)posted +44 min
Metabase Cloud is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud, Ashby +9"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana, JFrog +3"]:::blames
  root --> h4
  dr["Known dependency<br/>9 vendors<br/>Unbounce, Mapbox, Klaviyo, Webflow +5"]:::hop2
  root -.->|"depends on AWS"| dr
  me["Metabase Cloud (this incident)<br/>posted +44 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Metabase Cloud PlatformMetabase Store

Timeline of updates

  1. identified

    There is a problem with our cloud service provider that doesn’t let us create new instances of Metabase. We have identified the problem and we are waiting for the cloud service provider to restore its services.

  2. resolved

    AWS reports that the service should be normalized now

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: minor) posted by Metabase Cloud, started 2023-06-13 19:56 UTC, resolved after 3.3 h, 2 update(s).

Title
Problems when creating instances
Vendor
Metabase Cloud
Date
URL
https://rewindex.com/company/metabase-cloud/incidents/bbsf6jt53z14

Metabase Cloud profileRecent Metabase Cloud incidentsAll outages on June 13, 2023Metabase Cloud in June 2023MarkdownJSON