Companies / Metabase Cloud / changes

Metabase Cloud change history

11Major incident
When (UTC)ChangeKind
Critical incident: Metabase Store is unavailable
Metabase Store was unavailable from 2026-08-12 19:13 UTC to 2026-08-12 20:52 UTC, a critical outage lasting 1 h 39 min. Metabase reported maintenance on the Store infrastructure and subsequently marked the incident resolved.
Major incident
Major incident: Some Metabase functionality unavailable
Some functionality on the Metabase Cloud Platform was unavailable in an incident rated major by the vendor. It started at 2026-02-16 02:48 UTC and was resolved at 2026-02-16 03:15 UTC, lasting 27 min; no cause or fix was stated.
Major incident
Major incident: Some Metabase Cloud customers hosted in the EU are reporting their site is down or slowness
Some EU-hosted Metabase Cloud instances were down or slow in a major incident from 2025-04-02 13:00 UTC to 2025-04-02 21:34 UTC, lasting 8 h 33 min. Metabase reported service restored at 13:46 UTC and added monitoring while continuing work on the root-cause fix.
Major incident
Major incident: Metabase Store unavailable
Metabase Store had a major outage starting 2025-01-06 19:30 UTC, with a recorded duration of 0 min and status resolved. The vendor reported intermittent unavailability for an hour due to a problem during the store update, so the reported impact window differs from the recorded duration.
Major incident
Critical incident: Issue with SSL certificates
Metabase Cloud reported a critical certificate outage starting 2023-11-09 19:37 UTC, lasting 24 min. Hosted-instance users received invalid certificate errors after a Helm chart release CI misconfiguration replaced the external Nginx ingress certificate with a dummy certificate. Certificates were restored by 2023-11-09 20:02 UTC.
Major incident
Critical incident: Unable to create new Metabase cloud instances
Metabase Cloud customers could not create new cloud trials or cloud instances in a critical incident affecting Metabase Store. It started at 2023-07-28 13:10 UTC and was resolved at 2023-07-29 10:21 UTC, lasting 21 h 10 min; no cause or fix was stated.
Major incident
Major incident: Unable to create new database connections
Metabase Cloud customers could not add new databases or edit database connections during a major incident affecting Metabase Cloud Platform. It started at 2023-07-28 13:01 UTC and was resolved at 2023-07-29 09:06 UTC, lasting 20 h 4 min; no cause or specific fix was stated.
Major incident
Critical incident: Issue with Metabase Cloud
Metabase Cloud reported a critical outage blocking ingress network access to all instances, starting 2022-11-17 18:47 UTC and resolved at 2022-11-17 19:14 UTC (26 min). During new K8S cluster provisioning, DNS and load balancer configurations were accidentally overwritten; Metabase restored the correct configurations and added process controls and automated checks.
Major incident
Critical incident: Issues on our Cloud
Metabase Cloud Platform experienced downtime rated critical, starting at 2022-10-11 17:43 UTC and resolved at 2022-10-11 17:53 UTC (computed duration: 9 min). Metabase confirmed service was restored but did not state a cause or specific fix.
Major incident
Major incident: AWS Outage
A major Metabase Cloud Platform outage caused temporary downtime for a few customers due to an AWS us-east-1 issue. It started at 2021-12-07 17:39 UTC and was resolved at 2021-12-07 23:51 UTC, lasting 6 h 12 min; affected customers were operational after AWS restored most services.
Major incident
Major incident: Degraded service in our Business tier
Metabase Cloud reported major degradation affecting Business tier customers in isolated environments from 2021-08-10 16:37 UTC to 2021-08-10 20:38 UTC, lasting 4 h 1 min. A failed Elastic Beanstalk upgrade left instances inconsistent, with load balancers unable to mark them healthy and application servers continuously recycled; a fix was deployed before resolution.
Major incident